Help Center
Support
Open app

Testing context and variables

Test variables from the webhook, Outbound API and campaigns before real customers are called or call in.

Available in: ProIndividualLast reviewed on October 25, 2026

Variables make conversations personal, and that's exactly why you should test them. A placeholder that doesn't get filled disappears from the sentence, but the sentence then sounds incomplete. This page shows how to check variables for each source.

Where variables come from

SourceDirectionHow to test
Incoming WebhookinboundTest webhook on the Personality tab, then a real call
context of the Outbound APIoutboundStart Test Call on the Outbound tab
Columns of a campaignoutboundCampaign with a single contact, your own number

Outbound: test call with context

  1. Open your agent and switch to the Outbound tab.

  2. In the context field, enter a JSON object with your test values, for example:

    { "customer_name": "Anna Berger", "appointment": "15 January" }

  3. Click Start Test Call, choose the Sender number and enter your own number under Target number.

  4. Click Call and answer. The agent uses the values from the context.

Test calls to your own confirmed numbers work even before identity verification. The agent only calls other numbers once you've verified your identity under Billing.

In the prompt, the values appear in double curly brackets, such as "Hello {{customer_name}}, I'm calling about your appointment on {{appointment}}."

Inbound: testing the webhook

  1. On the Personality tab, open the Incoming Webhook section.
  2. Click Test webhook › Send test. bhomy sends a request with sample data to your URL and shows the response.
  3. Check that every field your prompt uses is in the response, spelled exactly the same way.
  4. Call your bhomy number from a phone your system knows. The agent should greet you with the values from your system.
  5. Call from a number your system doesn't know. Now the Fallback Values apply.

Checklist before going live

CheckExpected result
Every placeholder has a sourceWebhook field, context field or campaign column with the same name
Every placeholder has a fallback or a sentence that works without itNo broken-off sentence if the value is missing
Upper and lower case match{{First_name}} and {{first_name}} are different variables
No spaces inside the brackets{{first_name}}, not {{ first_name }}
Values sound natural when spoken"15 January" instead of "2026-01-15"

What you see in the call history

After the test, the call history shows the conversation with a transcript. You can tell from the agent's sentences whether it used the values correctly. The Main Logs tab lists the tools it used during the conversation.