Availability, Login-Only Access, Consent Text & Rate Limiting

1. Availability: Always Online / Offline Message / Scheduled Window #

The readme highlights:

• Availability options:
  • Always online
  • Offline message
  • Scheduled window

From the docs, Telegram settings include availability configuration so you can control when human mode is offered.

Typical behavior (per docs description):

• Always online:
  • Human mode can be used at all times when Telegram is enabled.
• Offline message:
  • Users may see that human support is currently offline.
  • The human mode may be disabled or show an informational offline notice.
• Scheduled window:
  • Human mode is available only inside specific time windows (as you configure).
  • Outside that window, the UI may show an offline or fallback message.

Step-by-step:

1. Go to Davix AI Engine → Chatbot → Telegram section.
2. Find the Availability setting.
3. Choose one of:
   • Always online.
   • Offline / custom message.
   • Scheduled times.
4. If schedule is used, configure the time window parameters.
5. Save changes.

image IMAGE PLACEHOLDER: Screenshot of the Telegram settings focus on “Availability” dropdown with options and, for scheduled, additional time fields. IMAGE image

2. Login-Only Option #

Docs (PDF) explicitly mention:

“If telegram_logged_in_only is enabled:
○ Only logged-in users can use human mode (checked via REST permission callbacks).”

Step-by-step:

1. In the Telegram settings, find Login-only for human mode (backed by a boolean like telegram_logged_in_only).
2. Turn it ON if:
   • You only want registered or logged-in users to get human help.
3. Save changes.

When this is active:

• REST endpoints validate that the request belongs to an authenticated user (nonce/cookie).
• If not, human mode is blocked and requests will fail permission checks.

3. Consent Text & Alerts #

Docs say you can configure consent:

“Configure availability, consent, rate limits.”

Readme also mentions:

“Consent text and alerts before sending messages to human agents.”

This ensures compliance and clarity by informing users that:

• Their messages are being forwarded to human staff via Telegram.
• Possibly that external systems are involved.

Step-by-step:

1. In Telegram settings, locate Consent Text or Warning message field.
2. Write a short, clear message explaining:
   • That messages will be sent to human agents.
   • That they may be handled via Telegram.
3. Save changes.

On the front-end:

• The chat uses this text to show a consent notice (either once or when switching to human mode, per your UI).

image IMAGE PLACEHOLDER: Screenshot of the chat showing a small consent notice above the input when user switches to Human mode. IMAGE image

4. Rate Limiting by IP #

Docs mention both:

• In readme: “Rate limiting by IP (maximum messages per time window).”
• In PDF: “check_rate_limit() uses WordPress transients.”

This means:

• The plugin keeps track of message counts per IP and time window.
• If a user exceeds the allowed number, the plugin can block or slow down further messages to human agents.

Step-by-step:

1. In Telegram settings, locate the Rate limiting fields:
   • Max messages per IP.
   • Time window (e.g., seconds/minutes).
2. Choose conservative values:
   • Enough to allow normal conversations.
   • Small enough to block abuse or spam.
3. Save changes.

Internally:

• check_rate_limit() uses WordPress transients to store counters.
• This keeps the rate limiting logic inside WordPress, no external storage required.