ceven

Mocean

Sends automated SMS and voice messages to customers, handles multi factor authentication codes, and routes incoming replies into your CRM based on intent.

Try Mocean in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Mocean integration

    • Describe the outcome and Ceven picks the right Mocean calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Mocean data, across all 6 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Mocean access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Mocean, when, and on whose behalf.
    • The agent pauses and asks when Mocean is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Mocean.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Mocean action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Mocean, and when to use it.

Send SMS
Use this when a workflow needs to push a text message to a customer phone number for alerts or updates.
Send Verification Code
Trigger a one time password for identity verification. Use this during sign up or password resets.
Verify Code
Check if the code provided by the user matches the Mocean verification record for that phone number.
Make Voice Call
Trigger an automated voice call to a specific number. Use this for high priority notifications that SMS might miss.
Get Message Status
Pull the current delivery state of a specific message ID to see if it was delivered or failed.
List Recent Messages
Pull a history of messages sent to or received from a specific phone number for context.
Search Messages
Query message logs by keyword or recipient to find specific customer conversations.
Update Sender ID
Change the alphanumeric sender name for a specific region to improve brand recognition.
Check Balance
Pull the current credit balance of the Mocean account to trigger low fund alerts.
Blacklist Number
Add a phone number to the block list to stop all outgoing communications to that user.
Remove from Blacklist
Restore communication capabilities for a previously blocked phone number.
Get Account Details
Pull general account settings and API limits to ensure workflow stability.

12 actions · scroll to see them all

Frequently asked questions

Ceven orchestrates the full verification loop. First, the agent calls the Mocean Send Verification Code action which generates a secure code and sends it via SMS. The agent then enters a wait state or listens for a webhook containing the user input. Once the user provides the code, Ceven calls the Verify Code action. If Mocean returns a success response, the agent proceeds to the next step in your workflow, such as granting account access or updating a profile. If the code is incorrect or expired, the agent can be configured to send a reminder or trigger a new code request automatically.
Yes, Mocean provides global reach, but delivery depends on the specific regulations of the destination country. Ceven can manage these complexities by utilizing different sender IDs based on the country code of the recipient. For example, if the agent detects a UK number, it can use a pre approved alphanumeric sender ID to ensure higher delivery rates. You should ensure your Mocean account has the necessary regional permissions enabled in your dashboard, as Ceven can only trigger messages to regions that your specific Mocean tier and account settings allow.
Ceven monitors the delivery status of every message sent. By using the Get Message Status action, the agent can detect failures such as invalid numbers or carrier blocks. You can build a fallback logic into your workflow. For instance, if an SMS fails, the agent can automatically trigger a Mocean voice call as a secondary channel. Alternatively, it can log the failure in your CRM and create a task for a human agent to reach out via email. This ensures that critical notifications always reach the customer regardless of the primary channel state.
Yes, Ceven processes incoming Mocean messages through webhooks. When a customer replies to an SMS, Mocean sends the data to Ceven, and the agent analyzes the text using natural language processing. You can define rules for how the agent responds. For example, if a customer replies Yes to a confirmation text, the agent can update a database record to confirmed. If the reply contains a question, the agent can draft a response based on your knowledge base and send it back through Mocean, creating a fully automated two way conversation.
Yes, Mocean imposes rate limits on the number of messages sent per second, which vary based on your account tier and the destination carrier. If a Ceven workflow attempts to blast thousands of messages at once, Mocean may return a rate limit error. To handle this, Ceven implements an exponential backoff strategy, meaning the agent will pause and retry the request after a short delay. For very large campaigns, we recommend using a queued workflow in Ceven to drip feed the messages at a pace that stays within your Mocean account thresholds.
Ceven uses secure API key management to connect to Mocean. When you provide your Mocean API credentials, they are encrypted at rest using AES 256 encryption. These keys are only decrypted in memory at the moment the agent needs to make a request to the Mocean API. No one at Ceven has access to your raw keys, and they are never exposed in the workflow logs or to the end users of your agents. You can rotate your Mocean keys at any time and update them in the Ceven integration settings to maintain security.
Yes, this is done through Mocean sender ID management. Depending on the country, you can use an alphanumeric string as the sender. In some regions, this requires a pre registration process with the local telecommunications authority. Once your sender ID is approved in the Mocean dashboard, you can use the Update Sender ID action in Ceven to ensure your messages appear under your brand name. This significantly increases open rates and trust compared to using a random long code or short code number.
Ceven can trigger the Make Voice Call action to initiate an automated call to a user. This is typically used for urgent notifications where an SMS might be ignored. You can provide the text to be converted to speech via the Mocean API. The agent can then track if the call was answered or if it went to voicemail. If the call is not answered, the agent can follow a predefined path, such as leaving a recorded message or escalating the alert to a human supervisor via a Slack or email notification.

Alternatives to Mocean

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Twilio logoTwilioMessageBird logoMessageBirdVonage logoVonagePlivo logoPlivo

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Mocean and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free