Skip to content

Going live

Publish to your shortcode, send answers to your own system, update a live app, and keep your wallet topped up.

Deploy your app

  1. Save your latest changes

    Deploy publishes the saved version, so press Save first.
  2. Press Deploy

    At the top right of the builder. If something needs fixing first, a list titled Fix these before you deploy names each screen; press Back to the flow, fix them, and try again.
  3. Enter your shortcode

    The code your aggregator assigned to you, such as *384*55#.
  4. Add a callback URL (optional)

    See the next section. Leave it empty if you don't need answers sent to your own system.
  5. Copy the callback address

    After Deploy, copy the address under Callback URL for your aggregator and paste it into your aggregator's dashboard. The link under it opens the setup guide for your aggregator.
Good to know: Two different addresses are involved, and it's easy to mix them up. The callback address Asterisks shows you goes into your aggregator's dashboard. The optional Callback URL you type is your system, where Asterisks sends answers.

Get answers in your system

If you enter a Callback URL (optional) when deploying (a full https:// address on your own server), Asterisks sends it every caller's answers when a session finishes on an End Session or Flash Alert screen. Use it to record orders, registrations or votes in your own database.

What Asterisks sends (POST, JSON)
{
  "sessionId": "ATUid_9f1c2...",
  "projectId": "your-app-id",
  "shortCode": "*384*55#",
  "phoneNumber": "233244123456",
  "status": "completed",
  "variables": {
    "cups": "2",
    "MobileNumber": "233244123456"
  },
  "completedAt": "2026-10-04T09:30:12Z"
}
  • variables holds every saved answer and every value saved from your APIs.
  • It is sent once, in the background, after the caller sees the last screen. Your server should reply within 5 seconds; it is not retried.
  • Sessions that are cancelled, time out, or end on Collect Payment don't send it.
Watch out: Treat the callback as a notification, not proof of payment. Check payments with your payment provider before delivering anything of value.

Making changes after launch

  1. Edit and test as usual

    Changes in the builder don't reach callers until you deploy. Test them in the phone preview first.
  2. Save, then Deploy again

    Enter the same shortcode. Callers get the new version from their next session.
  3. Re-enter your Callback URL

    Each deploy replaces the callback URL. If you leave the box empty on a redeploy, callbacks stop.

The callback address for your aggregator stays the same, so you don't need to change anything there.

Paying for sessions

Details
PriceGHS 0.025 per session (one call, from dial to last screen), however many screens it has.
Free sessionsEvery new account starts with credit for 100 sessions.
Monthly feeNone. You pay only for sessions.

Topping up

  1. Open Billing

    In the dashboard's left menu.
  2. Press Top up

    Choose an amount, or enter your own, then press Continue to payment.
  3. Pay

    Pay with mobile money or card. You return to a page that confirms your wallet has been topped up.
Watch out: When your wallet reaches zero, new callers see "Insufficient credits to run this session. Please top up." Top up before launch and keep an eye on your balance on the Billing page.

Settings → Usage history lists every top-up and session charge.

Keeping an eye on it

PageShows
OverviewToday’s sessions and the latest changes across your apps.
Live sessionsSessions as they happen. Keep it open while you test on a real phone.
Audit logsDeployments, sharing changes and other actions on your apps.
BillingYour wallet balance and recent charges.

What callers experience

When a caller…They see
replies with a number that isn’t on the menu“Invalid Input, try again.” and the menu again
gives an answer of the wrong typeThe reason (for example “Please enter a valid number.”) and the question again
replies 0The previous screen (unless you turned Pressing 0 goes back off)
gets disconnected, then dials again within 5 minutesThe screen they were on, so they don’t start over
reads a screen longer than 182 characters99. Next to see the rest, and 00. Back

Something not working? See Troubleshooting.