Field tokens inject contact and campaign data into the system prompt at call time. The AI uses real names, real products, and real context — not generic phrasing it had to fabricate because the data wasn't there.
Book a discovery callCampaign configuration fields and question text can include placeholder tokens — such as contacts.first_name or campaigns.campaign_goal — that are resolved at context assembly time. The token resolver expands all supported tokens to their live database values before the system prompt is built. The AI never sees a raw token.
The AI uses campaign fields in a defined priority order when answering objections and questions. The more you populate, the more precisely the AI can respond — without inventing anything.
contacts.first_name, contacts.last_name, and contacts.company are resolved from the contact record at call time. Use them in persona fields, question text, or campaign goal to make every message feel personal.
How it works: Contact name is available for context — the AI guardrail still prohibits using it in outbound messages (feels presumptuous on cold SMS).
campaigns.campaign_goal, campaigns.product_or_service, and campaigns.assistant_name are resolved from the campaign record. Use them to make a shared template work across multiple campaigns with different products.
How it works: All seven supported tokens are tested — multiple tokens in a single string resolve correctly.
The AI uses product_or_service, benefits, background, and objection_handling fields — in that priority order — when a contact asks a question the AI needs to answer. If no usable information is present, it deflects to a specialist rather than fabricating an answer.
How it works: No invented information is enforced via base guardrails — applies to every campaign without configuration.
When an operator saves campaign configuration containing an unknown or malformed token, the platform returns a 400 error with a descriptive message identifying the bad token. Unknown tokens are never silently passed to the AI.
How it works: Singular legacy tokens (contact.first_name without the 's') are flagged with a corrective hint pointing to the correct format.
We'll configure token fields, show you the resolved context, and run a test conversation.
Book a discovery call