You see everything before Phone Console makes any call. From the opening statement to potential objections and responses, you have complete visibility and control over what will be said - and you can even hear a preview before giving final approval.
The Script Generation & Approval Process
When Research Console determines your Problem needs a phone call, here's the step-by-step workflow:
1. Research Console Gathers Context
Research Console analyzes your Problem, reviewing all facts, evidence, and goals gathered so far. It identifies:
Who needs to be called
What the objective is
What information to reference
What tone would be most effective
2. Persona Console Prepares (Optional)
If helpful, Research Console may recommend using Persona Console to role-play the conversation before writing the script. With your permission, Persona Console simulates:
How the representative might respond
Likely objections or pushback
Follow-up questions they might ask
Best strategic responses
You approve before this happens.
3. Compose Console Writes the Script
Compose Console then drafts a complete call script tailored to your situation, including:
The goal of the call
Opening statement with identification and reason for calling
Key talking points to hit during the conversation
Potential objections the representative might raise
Pre-written responses to those objections
Desired outcome and next steps
4. You Review & Approve
The script appears in your Problem Dashboard for review. You'll see:
Every word of the opening statement
All anticipated conversation paths
How Phone Console will respond to common objections
The emotional tone being used
Any dynamic capabilities enabled (like small talk)
Nothing happens until you approve it.
What You See in the Script
When reviewing a Phone Console script, you'll have access to:
Core Script Elements:
Opening introduction - Exactly how Phone Console will identify itself
Purpose statement - What Phone Console will say the call is about
Key information - Account numbers, dates, references it will provide
Main talking points - The strategic arguments or requests
Desired outcome - What Phone Console is trying to achieve
Anticipated Responses:
Potential objection #1 → Pre-written response
Potential objection #2 → Pre-written response
Potential objection #3 → Pre-written response
And so on...
Behind-the-Scenes Data (Optional Deep Dive):
If you want to see how decisions were made, you can review:
Research Console's thinking - Why this approach was chosen
Persona Console's role-play data - What scenarios were rehearsed
Strategic reasoning - The logic behind tone, timing, and approach
Most users stay at the surface level - but power users can dive as deep as they want.
Making Edits to the Script
If you want to change something, you have options:
Guided Editing:
You can request specific changes to the script
The system reviews your edits to prevent compliance issues (e.g., claiming to be a lawyer)
Edits show as "Pending" while being processed
Once approved by the system, the updated script is ready
Change the Emotional Tone:
Don't like the tone? Switch it (Professional → Frustrated, Firm → Exhausted, etc.)
Compose Console regenerates the script with the new tone
Review and approve again
Regenerate Entirely:
Request a completely different approach
Provide additional context or instructions
Get a fresh script based on your guidance
Why system approval? To protect you and Loophole from misuse - like editing a script to say "This is John Doe's lawyer and I'm going to sue you!" - which would violate UPL compliance and our Terms of Service.
Dynamic Capabilities & "On-the-Fly" Responses
Phone Console isn't limited to reading the script word-for-word. It can adapt naturally during the call while staying firmly within your approved boundaries.
Small Talk Setting:
You'll see a setting like "Small Talk: ON" in your script review.
ON: Phone Console can engage in brief, natural small talk if prompted
Representative: "How's your Saturday going?"
Phone Console: "Well, it's a bit rainy today, so I'm staying inside trying to stay dry. How about you?"OFF: Phone Console stays strictly professional and redirects to the purpose of the call
Adaptive Responses:
If the representative says something unexpected, Phone Console can:
Respond naturally within the boundaries you've set
Reference information you've approved
Stay on strategy without sounding robotic
You'll see these settings clearly before the call - and you can change them if you prefer Phone Console to stick more rigidly to the script.
Setting Boundaries
You can define what Phone Console should never do or say:
Per-Problem Boundaries:
Set specific rules for individual calls:
"Never mention the price"
"Don't agree to anything without asking me first"
"Avoid discussing the prior representative"
Account-Level Boundaries:
Set global rules that apply to all Phone Console calls:
"Always deflect or avoid political topics"
"Never use profanity, even if frustrated"
"Decline to answer questions about [specific topic]"
These boundaries ensure Phone Console operates exactly within your comfort zone.
Preview the Audio BEFORE Final Approval
This is the game-changer: After approving the script, you can hear what Phone Console will sound like BEFORE it actually makes the call.
Here's how it works:
Review and approve the written script in your Problem Dashboard
Choose to "Preview Audio" or "Hear Sample"
Listen to Phone Console deliver the opening statement and key lines in the selected tone
If you like it → Give final approval for the actual call
If you don't like it → Go back and adjust tone, pacing, or script
You never have to guess what Phone Console will sound like. You hear it first.
After the Call: Full Transparency
Once Phone Console completes the call, you'll see:
Call Summary:
Outcome: What was achieved
Reference numbers: Case IDs, confirmation numbers obtained
Next steps: What the representative committed to
Follow-up needed: If any additional action is required
Full Transcript:
A complete text record of the conversation, showing:
What Phone Console said
What the representative said
Objections raised and how they were handled
Any deviations from the script and why
Recording (Optional):
You can choose to record calls if you want an audio record.
Important: Recording phone calls has different legal requirements in different states:
Some states require one-party consent (only you need to know)
Some states require two-party consent (the other person must be informed)
It is your responsibility to ensure recording is legal in your jurisdiction before enabling this feature. Loophole is not responsible for verifying legality of recordings.
What Happens If Something Goes Wrong?
If Phone Console encounters an unexpected question or situation it doesn't have information for:
Acknowledges professionally: "That's a good question, let me verify that information to make sure I give you the correct details."
Offers to call back: "Can I get back to you within [timeframe] with that information?"
Reports back to you: Phone Console documents the question in your Problem Dashboard
You decide next steps: Provide the information, adjust strategy, or end the campaign
Phone Console never makes up information or misrepresents facts.
Summary: Complete Visibility & Control
You know exactly what Phone Console will say because:
✅ You see the full written script before approval
✅ You review anticipated objections and responses
✅ You can make guided edits or change the tone
✅ You can set boundaries and "never say" rules
✅ You can preview the audio before the actual call
✅ You see a full transcript after the call
✅ You can record if you choose (legal responsibility is yours)
Nothing is hidden. Nothing is automatic. You're always in control.
