Mocean

@Mocean send an SMS to +60123456789 with the message 'Your verification code is 847291. Valid for 10 minutes.'

SMS sent successfully via Mocean. Message ID: msg_9k3j2h1f. Delivered to +60123456789 at 2024-01-15 14:32:07 UTC. Character count: 62 (1 segment). Delivery status: accepted by carrier. You can track this message in your Mocean dashboard under outbound messages.

This example shows the core SMS delivery capability. Requires valid API credentials with send permissions and sufficient account balance. Messages are charged per segment (160 characters for GSM-7, 70 for Unicode). Delivery confirmation is carrier-dependent and may take seconds to minutes.

@Mocean check the delivery status for message ID msg_9k3j2h1f and show me the current account balance

Message msg_9k3j2h1f status: delivered at 2024-01-15 14:32:19 UTC (12 seconds after submission). Recipient confirmed receipt. Your Mocean account balance: $47.35 USD. This covers approximately 2,840 standard SMS segments at current rates. Last top-up was $50.00 on 2024-01-10.

Demonstrates read operations for message tracking and account monitoring. Delivery timestamps depend on carrier response speed. Balance checks help prevent service interruption during high-volume campaigns. Status updates may lag by 30-60 seconds for some carriers in certain regions.

@Mocean analyze the last 50 outbound messages and summarize delivery success rate by country code, flagging any patterns in failed deliveries

Analyzed 50 messages sent between 2024-01-10 and 2024-01-15. Overall delivery rate: 94% (47 delivered, 3 failed). Breakdown by country: Malaysia (+60): 38 sent, 37 delivered (97.4%). Singapore (+65): 12 sent, 10 delivered (83.3%). Failed messages: 2 to Singapore numbers showed 'invalid number' errors, 1 Malaysia message timed out after 48 hours. Recommendation: validate Singapore numbers against current registry before sending.

Combines Mocean's message history retrieval with AI analysis to surface operational insights. Useful for troubleshooting delivery issues or optimizing send strategies. Requires access to message logs (typically retained 30-90 days). Analysis quality depends on sample size and time range selected.

When you need transactional SMS without building your own gateway

A 6-person DevOps team needs to send alert texts when deployments fail or servers go down. They don't want to manage Twilio credentials across three environments or write retry logic for SMS delivery. Mocean handles the message queue and delivery receipts through a single API key. The trade-off: you're locked into Mocean's rate limits and regional coverage, so if you're sending 10k+ texts a day or need guaranteed delivery in Southeast Asia, verify their SLA first. For most small teams sending a few hundred operational alerts a month, the simplicity wins. If your alert volume is under 500 texts per day and you want one less vendor to audit, Mocean keeps the pipeline clean.

When your signup flow needs two-factor codes without telecom overhead

A 4-person SaaS startup is adding phone verification to their signup form. They need to send a 6-digit code, wait 90 seconds, maybe resend once. They don't need voice calls, don't need to parse replies, and don't want to negotiate carrier contracts. Mocean's API key auth means the backend engineer can wire this up in an afternoon without touching OAuth or webhook signatures. The constraint: if you later want to handle inbound SMS replies or build a full conversational flow, you'll outgrow this fast. For one-way verification codes sent to under 1,000 users a week, Mocean does the job without the Twilio learning curve. If you're just checking that the phone number is real, this is the right scope.

When you're sending batch reminders and need delivery tracking

A 3-person nonprofit runs monthly meetups and wants to text 200 RSVPs the day before each event. They need to know which messages bounced so they can follow up by email. Mocean's delivery receipts let them log failures without building a webhook listener or polling a status endpoint. The catch: if you're personalizing each message with custom fields pulled from Airtable or need to throttle sends across time zones, you'll write that logic yourself—Mocean doesn't template or schedule. For straightforward batch sends under 500 recipients where you just need proof of delivery, the API key model keeps it simple. If your list is static and your message rarely changes, this handles the last mile.