Skip to content

Document simulating a call from a specific phone number - #1292

Merged
scott-lowe-vapi merged 1 commit into
mainfrom
scottlowe/sim-caller-phone-number-docs
Oct 6, 2026
Merged

scott-lowe-vapi merged 1 commit into
mainfrom
scottlowe/sim-caller-phone-number-docs

Conversation

@scott-lowe-vapi

Copy link
Copy Markdown
Contributor

Description

  • Adds a short "Simulate a call from a specific phone number" subsection to the simulations advanced page, under "Set variable values". Customers testing caller-authenticated flows (caller identified by {{customer.number}}, then a tool looks up their account) have asked how to do this more than once, and support needs a page to point them to.
  • Shows the API override (targetOverrides.variableValues.customer.number) with one PATCH example and a line on transient scenarios. It's API-only because the Variables tab stores flat text names and values, which can't express the nested customer.number.
  • Documents two limits, both checked against the platform code:
    • The override replaces the whole customer variable, so any other customer.* fields the assistant uses must be set too.
    • The override only affects {{customer.number}} template resolution. Simulations never set call.customer, so a tool that reads the caller from the server message payload won't see it.
  • Adds a troubleshooting row, "A tool looks up the wrong caller", linking to the new subsection.

Testing Steps

  • Run the app locally using fern docs dev or navigate to preview deployment
  • Ensure that the changed pages and code snippets work

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@lightsage-app

lightsage-app Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

Lightsage docs evals

Lightsage could not queue docs evals for this PR.

Docs URL: https://vapi-preview-01a11382-43dd-76d7-a6da-e37df6385a4c.docs.buildwithfern.com
Commit: 9fd6723
Reason: No custom evals are selected for GitHub PR evals. Open Lightsage > Custom Evals and enable the GitHub checkbox for at least one custom eval.

@github-actions

github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

@scott-lowe-vapi
scott-lowe-vapi merged commit c970d63 into main Oct 6, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants