Teltel

@Teltel show me all inbound calls from the last 24 hours that lasted longer than 5 minutes

Found 12 inbound calls in the last 24 hours exceeding 5 minutes. Top results: Call from +1-555-0142 at 2:34 PM (duration 8m 22s, answered), +1-555-0891 at 11:17 AM (duration 12m 5s, answered), +1-555-0267 at 9:45 AM (duration 6m 41s, voicemail). All calls show 'completed' status. The longest call was 18 minutes from +1-555-0334. This is an illustrative example based on typical Teltel call log structure.

This example demonstrates filtering call records by time range, duration, and direction. Teltel's API requires an API key with read access to call logs. Results are paginated; this prompt retrieves the first page. Actual call metadata depends on your account's telephony activity and retention settings.

@Teltel pull SMS messages sent to +1-555-0198 in the past week and summarize the conversation thread

Retrieved 8 SMS messages to/from +1-555-0198 over the past 7 days. Outbound: 5 messages (all delivered). Inbound: 3 messages. Thread summary: Initial outreach on Monday about appointment confirmation, customer replied Tuesday requesting reschedule, follow-up confirmation sent Wednesday, customer confirmed Thursday. Most recent message was Thursday 3:22 PM. This is an illustrative example of how Teltel returns SMS logs with status and timestamp metadata.

This example combines SMS retrieval with AI synthesis to create a conversation summary. Requires API key with SMS read permissions. Teltel returns messages in chronological order with delivery status; the AI interprets the thread context. Useful for customer service teams reviewing communication history before callbacks.

@Teltel list all users in our account and flag anyone who hasn't been assigned a phone number yet

Found 23 users in your Teltel account. 19 users have assigned phone numbers. 4 users without assignments: Sarah Chen (user ID: usr_8x2k, created Jan 15), Mike Torres (user ID: usr_9p4m, created Jan 18), Emma Liu (user ID: usr_1a7n, created Jan 22), James Park (user ID: usr_3r5q, created yesterday). All unassigned users have 'active' status but no telephony resources provisioned. This is an illustrative example based on typical Teltel user record structure.

This example shows user account synchronization and AI-driven filtering logic. Teltel's user list includes metadata like creation date and resource assignments, but the 'flagging' logic happens in the AI layer. Useful for onboarding audits or provisioning workflows. Results are paginated; accounts with 100+ users will need multiple queries.

When call logs close the loop on escalation handoffs

A 6-person support team fields 40-60 calls a day and routes escalations to engineering via Slack threads. The Get Call List tool pulls duration and status for every inbound call in the last 24 hours, so the team lead can spot patterns—three 8-minute calls from the same customer number usually means a P1 bug, not user error. Switchy surfaces those clusters in a morning digest without anyone opening the Teltel dashboard. This works if your call volume stays under 200 a day and you're not doing real-time sentiment analysis; beyond that threshold, you need a proper call-center platform with transcription. If your team already lives in Zendesk or Intercom and just needs call metadata to enrich tickets, this MCP closes the gap.

When you need inbound SMS in the same workspace as campaign metrics

A 3-person marketing team at a local-services startup sends appointment reminders via SMS and wants to track opt-outs and confirmation replies without switching tools. The Get SMS List and Receive Inbound SMS tools let Switchy pull the last 500 messages and flag keywords like 'STOP' or 'YES' in a shared thread. The team reviews responses during weekly planning and adjusts send times based on reply velocity. This setup breaks down if you're sending more than 2,000 messages a month or need compliance workflows—Teltel's API doesn't expose delivery receipts or carrier metadata, so you're flying blind on deliverability. For low-volume campaigns where the team just needs to see replies in context, this MCP keeps SMS in the same workspace as your other metrics.

When provisioning phone numbers means reconciling two user lists

A 10-person ops team provisions phone numbers for field technicians and needs to confirm that every active employee in the HRIS has a corresponding Teltel user. The Get Users List tool pages through the Teltel account and surfaces mismatches—new hires without numbers, deactivated employees still holding lines. Switchy runs this check every Monday morning and posts discrepancies to a Slack channel so the ops lead can fix provisioning gaps before payroll closes. This works if your headcount is under 200 and turnover is predictable; larger teams need a proper identity-management integration with automated deprovisioning. If you're manually reconciling user lists once a week and the stakes are 'wasted line fees' rather than 'compliance violation', this MCP saves 20 minutes of spreadsheet diffing.