Testing Workspace

Qualification Agent Console

SubmissionLoading…
CampaignsLoading…
VoiceLoading…

Create a transfer session against the current campaign routing layer, verify agent access, and stage a live call for the Twilio handoff path. The form prefers direct Supabase intake when browser auth is available and falls back to the local Node API when it is not.

Create Transfer Session

Enter the same metadata your human qualifier has before warm-transferring the homeowner into the AI desk.

Transfer LineLoading…
The console checks the public bootstrap function first, then falls back to the local runtime config when needed.
Use the service label expected by your campaign routing.
Use the same mobile number the caller will transfer from so ANI matching can work.
Campaigns come from direct Supabase access or the Node fallback.
Include the city so the desk identity and confirmation prompt stay aligned.
Helpful for testing, but not required to stage a session.
Loading runtime configuration and campaign access.

Transfer Output

Review the staged session, confirm the transfer line, and keep the claim token ready if caller ID is stripped during the handoff.

Waiting for a Session

Create a session to populate the live transfer number, session ID, claim token, and the AI desk identity selected for this call.

Session ID

Not Ready

Claim Token

Not Ready

AI Transfer Number

Not Ready

Created

Not Ready

  1. Stage the caller. Create the session before the live attended transfer begins.
  2. Warm-transfer to the AI line. Use the number shown above after the session returns successfully.
  3. Use the claim token only if needed. If ANI is stripped, say or key in the returned six-digit token. 
No response yet.

Runtime Overview

Current transport, config source, and persistence mode for this testing session.

Config Source

Loading…

Submission Path

Loading…

Campaign Source

Loading…

Persistence

Loading…

Voice Runtime

Loading…

AI Number

Loading…

Agent Authentication

Browser auth is optional for local testing, but direct Supabase intake requires a valid agent session.

Checking Agent Access

The console will use direct Supabase intake when browser-safe config and an active agent session are available.

Browser Auth: Loading…
Agent Status: Loading…