Skip to main content

InboundLeadConfig

Controls lead creation and the optional acknowledgement sent before the main generated reply.

stage_id object

Pipeline stage assigned to a lead created from an inbound message. Null falls back to the agent's initial pipeline stage, then the product's first stage.

anyOf
integer
quick_reply_enabledQuick Reply Enabled

Whether to send the quick reply for a newly created inbound lead dialogue or an eligible replacement support-ticket dialogue after response eligibility checks pass.

Default value: false
quick_reply_textQuick Reply Text

Jinja template rendered from lead CRM fields and sent immediately before main reply generation. Replacement support tickets use a server-configured closure cooldown. Blank text disables the quick reply.

Default value:
reply_to_start_enabledReply To Start Enabled

Whether to send a canned reply when a new dialogue opens with a bare "/start" message (common from Telegram/Max bots). When it fires it replaces the generated reply for that turn and takes precedence over the quick reply.

Default value: false
reply_to_start_textReply To Start Text

Jinja template sent in response to a "/start" opener (matched on the first token, so deep links like "/start " also qualify). Blank text disables it, and "/start" is then handled as an ordinary message with a normal generated reply.

Default value:
InboundLeadConfig
{
  "stage_id": 0,
  "quick_reply_enabled": false,
  "quick_reply_text": "",
  "reply_to_start_enabled": false,
  "reply_to_start_text": ""
}