How to Make a Test Call

Why Test Call

A test call is the fastest way to confirm that a
tracking number, the Offer it routes to, and the Buyer
it targets are all configured correctly. The test call
creates a real Call record, so you can inspect the full
routing trace, the recording, and the billing outcome
afterward.

Procedure

1. Open the Number detail page at /numbers/:id and note the international formatted number.
2. From any phone, dial that number. Use a phone not previously associated with the company so the call is treated as a fresh caller rather than a repeat.
3. Let the call complete. If the Offer routes to a buyer, the buyer phone will ring. Answer the buyer leg to establish the call.
4. Hang up. The Call record is now finalized.

Reviewing the Result

Navigate to Calls -> Call Logs (/calls) and open the
most recent entry. The Call detail page shows:

• The top-level status (for example finished, no-buyer, not-open, rejected, caller-hung-up, failed) and the computed sub-status (for example no-buyer-all-maxed-out, no-buyer-all-filtered, no-buyer-prevent-dupes, hold-queue-hung-up, ivr-no-keypress, caller-hung-up-while-ringing-buyer).
• The routing timeline showing which buyers were attempted and why each one succeeded or failed.
• The recording, if recording is enabled on the Offer.
• The transcription, if transcription is enabled.
• The conversion outcome and any tokens captured.

Troubleshooting

If the call did not route as expected, the sub-status
on the Call record is the single most useful piece of
information. Sub-status values are computed from the
call's log trail, so each value maps to a specific
reason in routing (for example
no-buyer-all-maxed-out means every eligible buyer was
at its concurrency cap, and no-buyer-all-filtered
means every buyer was excluded by filters such as
token value mismatches).