All guides
User

WhatsApp Chatbot Builder

Screen guide

Before you start

Use the account and workspace that own the relevant records. The feature also needs to be enabled for this installation and plan.

Open this feature
  1. Open /portal/whatsapp-hub/chatbot-builder on your site.

Steps

Use Save settings

  1. Open /portal/whatsapp-hub/chatbot-builder on your application domain, using the workspace account for this task.
  2. Find the form containing Enable WhatsApp chatbot, Enable fallback reply, Throttle minutes. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Save settings. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
Enable WhatsApp chatbotEnter the enable whatsapp chatbot for this task, using the help or example shown by the form. Allow inbound WhatsApp messages to trigger saved rules.
Enable fallback replyEnter the enable fallback reply for this task, using the help or example shown by the form. Send a default reply when no keyword rule matches.
Throttle minutesRequired. Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Prevent repeated bot replies in the same conversation for this many minutes. Minimum 0. Maximum 1440.
Fallback replyOptional unless the current form requests it. Enter the fallback reply for this task, using the help or example shown by the form. The form’s example is Thanks for messaging us. A team member will reply soon.. Replace it with your own value. Maximum 2000 characters.

Create or update: Save rule / Create rule

  1. Open /portal/whatsapp-hub/chatbot-builder on your application domain, using the workspace account for this task.
  2. Find the form containing Rule name, WhatsApp account, Match type. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Use the button shown for the current state: Save rule, Create rule. Creation and editing can show different labels; submit the form once.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
Rule nameRequired. Enter the rule name for this task, using the help or example shown by the form. Maximum 120 characters.
WhatsApp accountOptional unless the current form requests it. Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving.
Match typeRequired. Enter the match type for this task, using the help or example shown by the form.
Audience stageRequired. Enter the audience stage for this task, using the help or example shown by the form.
Keyword or phraseRequired. Enter the keyword or phrase for this task, using the help or example shown by the form. Maximum 255 characters.
PriorityRequired. Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 1. Maximum 999.
Reply textRequired. Enter the reply text for this task, using the help or example shown by the form. Maximum 2000 characters.

Fields and choices

Field descriptions appear beside each task above so that separate forms are not mixed together.

Check the result

  1. Stay in the same account/workspace and reopen the intended record or result screen.
  2. For saved settings, compare the displayed values with the choices you made. For filters and previews, check the current result scope.
  3. For queued or external work, inspect its status/history and provider result where applicable. A successful save does not by itself prove message delivery, publication, payment completion or provider approval.

Common problems

ProblemWhat to check
The screen or action is missingCheck the correct workspace account, role, enabled app and plan. A hidden action is not fixed by typing an internal endpoint.
A field is rejectedRead its validation message, choose from the offered options and check the relevant format or limit. Do not substitute a database ID for a displayed choice.
A list is emptyCheck the selected workspace, search text, date range and status filters. Clear one filter at a time before concluding that records are missing.
A request is still pendingCheck its status/history before repeating it. For messages, publishing, imports and payments, a submitted request can finish later or fail separately.

Technical reference

Role-scoped source references

Pinned commit: 68a5655db1bbe17c74fb211f0fe0ee4e63c8be88

    Source-only route information
    MethodSource-default route