When software needs a human

Push notifications with rich content and replies

Roundtrip lets apps and agents send notifications, cards, forms, and requests to people’s phones. Users respond with a tap, form, or message, and every response goes back to your app.

The problem

Sending notifications is still harder than it should be

Most channels come with setup pain, plain-text limits, and no clean way to collect a response.

SMS

Stand up Twilio, buy numbers, and clear A2P registration before a single text sends. It is one-way, so a reply is just more text to parse.

WhatsApp

Apply for Business API access, get message templates approved, and wait. Anything interactive lives inside Meta's rules, not yours.

Telegram

It is a chat app, so you are stuck with text messages. No real cards or forms, just a bot typing lines into a conversation.

Email

Easy to send, easy to bury. It sits unread for hours, and a reply comes back as free text you still have to read and route by hand.

Slack

Overkill for a single ask. It is a whole team chat tool, not a clean way to send one request and get one decision back.

Custom mobile apps

Push notifications, sign-in, app review, and two codebases to maintain. Months of work before anyone can tap Approve.

Push to a Roundtrip channel, and subscribers get notified on mobile.

Sending a Roundtrip push notification is a simple HTTP request. No carriers to configure. No mobile apps to build. No approval queues to wait on.

How it works

Send a notification users can act on

Roundtrip sends notifications, cards, forms, and requests to your users’ phones. Users respond in the app, and every response goes back to your webhook.

Send to a channel

Make one HTTP request with a notification, channel, and optional card or form. Roundtrip delivers it to the right users.

Show rich content

Notifications open into mobile cards with context, actions, forms, summaries, and detail views.

Get a response back

Users tap a button, submit a form, or reply with a message. Roundtrip sends the result back to your app.

Use cases

Notifications that open into workflows

Roundtrip is for the moment software needs a human: a deploy to approve, an incident to own, an agent waiting on a yes. The notification carries the context, and the decision comes back to you.

Channels

Notifications, grouped into channels

A channel is just a topic, like in Slack. Your users follow the ones they care about. Push to a channel and everyone following it gets the notification.

# deploysShip and rollback notices for the team
# alertsThings that are on fire right now
# ordersNew orders and ones that need a look
# supportQuestions coming in from customers
# personalJust your own reminders and notices
Rich content

Notifications with cards and forms

Each notification can include a card with the context users need. Show a short version in the feed, open a full view for details, and collect a response when needed.

9:41
#approvals

Acme Corp · Quote #0042

$44,000. Needs your sign-off before it goes out.

Amount$44,000
OwnerPriya Shah
Expiresin 2 days
POST /roundtrip/v1/requests200 OK
{
  "channels": [
    "approvals"
  ],
  "notification": {
    "title": "Acme Corp · Quote #0042",
    "body": "$44,000. Needs your sign-off before it goes out."
  },
  "content": {
    "title": "Acme Corp · Quote #0042",
    "description": "$44,000. Needs your sign-off before it goes out.",
    "sections": [
      {
        "type": "list",
        "items": [
          {
            "label": "Amount",
            "value": "$44,000"
          },
          {
            "label": "Owner",
            "value": "Priya Shah"
          },
          {
            "label": "Expires",
            "value": "in 2 days"
          }
        ]
      }
    ],
    "actions": [
      {
        "id": "approve",
        "label": "Approve",
        "style": "primary"
      },
      {
        "id": "reject",
        "label": "Reject",
        "style": "destructive"
      }
    ]
  },
  "response": {
    "mode": "optional",
    "webhook": "https://api.example.com/cb"
  }
}

Build a request like this

Compose blocks in the visual builder, or point your agent at the API.

Build your own
User actions

Getting responses back

Whether users tap, submit a form, or reply, Roundtrip sends a signed event to your webhook and retries until it lands.

In the appA tap

Approve the $44k quote for Acme?

POST https://api.example.com/cbsigned
{
  "requestId": "k1234…",
  "channel": "agent-tasks",
  "kind": "tap",
  "action": "approve",
  "metadata": { "quoteId": "0042" },
  "submittedAt": "2026-06-19T16:41:09Z"
}
Pricing

Pricing that starts small and scales with usage

Start with a limited trial. Upgrade when Roundtrip becomes part of your workflow.

Developer

Small projects, prototypes, and personal workflows.

$5/ month
  • 10k basic notifications / month
  • 1k rich requests / month
  • 3 channels
  • 1GB attachment storage
  • 30-day history
  • Signed webhooks

Pro

Recommended

Production apps, agents, and internal tools.

$19/ month
  • 100k basic notifications / month
  • 10k rich requests / month
  • 25 channels
  • 25GB attachment storage
  • 90-day history
  • Delivery logs and retries
  • Email support

Scale

High-volume and business-critical workflows.

$99/ month
  • 1M basic notifications / month
  • 100k rich requests / month
  • Unlimited channels
  • 250GB attachment storage
  • 1-year history
  • SSO and audit logs
  • SLA and priority support

Trial

Start with 1,000 trial requests. No credit card required. Test notifications, cards, forms, actions, and webhooks before upgrading.

Basic notifications are simple pushes with a title, body, and link. Rich requests include cards, forms, actions, replies, and webhook responses. End users are free.

Send your first notification

Get an API key and push to a channel in the next few minutes.