Callpage

@callpage show me all active widgets on our account and which managers are assigned to each one

Found 4 widgets across your Callpage account. Widget #3409 ('Homepage CTA') has 3 managers assigned: Sarah Chen, Mike Torres, and Alex Kim. Widget #3410 ('Pricing Page') has 2 managers: Sarah Chen and Jordan Lee. Widget #3411 ('Contact Form Fallback') has 1 manager: Mike Torres. Widget #3412 ('Blog Sidebar') currently has no managers assigned. This example illustrates typical output when querying widget configuration — actual widget IDs, names, and manager assignments will reflect your account's current state.

This example combines two read operations: fetching all widgets, then retrieving manager assignments for each. Requires valid API_KEY with read access to widgets and users. Useful for auditing callback routing before a campaign launch, but note that manager availability schedules aren't shown here — you'd need separate queries to verify who's actually online.

@callpage create a new widget for our demo request page and set up a custom voice greeting that says 'Thanks for your interest in our enterprise plan'

Created widget #3413 and generated a custom voice message (ID: vm_8472). The widget is now ready to embed on your demo request page using the provided JavaScript snippet. The voice greeting will play after a visitor requests a callback, before connecting to an available manager. This example shows the two-step setup process — actual widget IDs and voice message IDs will differ. You'll need to manually add the embed code to your site's HTML.

This write operation creates persistent resources in your Callpage account. The voice message creation requires specifying a locale (defaults to 'en' if not provided). Be aware that creating widgets doesn't automatically assign managers — you'd need a follow-up action to route callbacks, or visitors will see 'no agents available'. Widget deletion requires the exact ID, so keep track of test widgets.

@callpage pull all SMS templates for widget 3409 and draft a new custom message that's more casual for our startup audience

Retrieved 3 SMS templates for widget #3409. Default template: 'Your callback request has been received. A manager will contact you shortly at [phone].' Custom template 1: 'Thanks for reaching out! We'll call you at [phone] within 5 minutes.' Custom template 2: 'Got your request — calling [phone] now!' Based on these, here's a casual draft: 'Hey! Just got your callback request 👋 We'll ring you at [phone] in the next few mins. - The [Company] team'. This example shows how the AI can synthesize existing templates into new variations while preserving required placeholders like [phone].

This synthesis example pairs Callpage's SMS retrieval with the AI's copywriting. The draft isn't automatically saved — you'd need to manually create it via Callpage's interface or a separate API call (if supported). Note that SMS templates must include the [phone] placeholder to function correctly, and character limits may apply depending on your SMS provider. Casual tone may not suit all industries.

When Callpage fits a 2-5 rep outbound sales motion

A four-person sales team at a B2B SaaS company wants callback widgets on their pricing and demo pages. Callpage is the right call here: one person creates the widget, assigns the four reps as managers, and writes custom voice messages for different page contexts. The 17-tool scope covers widget CRUD, manager assignment, and message templates—everything needed to wire up a multi-rep callback flow without touching vendor UI. The threshold: if your team runs more than 8-10 widgets across different sites or brands, you'll spend more time paginating through Get All Widgets than the automation saves. For a single-site, small-team callback setup, Callpage's MCP turns a 20-minute UI task into a 90-second Switchy prompt.

Use this MCP to audit callback config across regions

A 12-person customer success org runs Callpage widgets in three languages across EMEA, APAC, and Americas sites. They need to verify that each widget has the correct managers assigned and that SMS templates match regional compliance rules. The Get All Widgets, Get All Managers, and Get All SMS Messages tools let a CS ops lead pull the full config into Switchy, compare it against a compliance checklist, and flag mismatches—all in one conversation. This beats logging into Callpage's dashboard and clicking through 15+ widgets by hand. The catch: if your callback volume is low enough that you only check config quarterly, the MCP is overkill. For monthly or sprint-based audits at multi-region scale, it's a 10-minute win.

When you need to delete orphaned callback widgets fast

A three-person marketing team at a Series A startup has 22 Callpage widgets live across their site, but only 9 are still in use—the rest are from old landing pages or A/B tests. They want to delete the orphans without risking the active ones. The Get All Widgets and Delete Widget by Id tools let them list every widget, cross-reference against their site map in Switchy, and delete the dead ones in a single session. This is faster and safer than clicking through Callpage's UI, where it's easy to lose track of which widget ID maps to which page. The trade-off: if you only have 3-4 widgets total, just use the vendor dashboard. For 15+ widgets and a cleanup cadence of once per quarter, the MCP saves 30 minutes and prevents accidental deletions.