Arino One documentation

Everything needed to run a dedicated Arino One instance — provisioning, the managed Infobip back-end, every channel, GDPR operations and troubleshooting.

Search runs over every published article. AI answers coming soon.

Getting started

Create your Arino One instance, invite your team, and send the first message.

1 article →

Remix the template

Fork the Arino One front-end template, rebrand it, and connect it to your instance.

Coming soon →

Infobip

Connect and operate the managed Infobip back-end behind your instance.

2 articles →

Channels

WhatsApp, Instagram, Messenger, SMS, RCS, Email, live chat and PingMe.

2 articles →

Guides

End-to-end walkthroughs for campaigns, automations, CDP and QR opt-in.

Coming soon →

Account & services

Billing, instance sizing, regions, support tiers and service management.

Coming soon →

Compliance

GDPR operations: consent, retention, erasure, DPA and audit evidence.

Coming soon →

Troubleshooting

Diagnose delivery failures, template rejections, webhooks and sync errors.

Coming soon →

Reference

Glossary, changelog and frequently asked questions.

Coming soon →
Popular articles
Infobip and Lovable: how it works, and how to connect
How an Arino One instance on Lovable uses Infobip to send and receive across WhatsApp, SMS, and other channels — and how to connect your own Infobip account with an API key and base URL.
Create your Arino One instance
Request, provision and open your dedicated Arino One instance — from account creation to first sign-in to your console.
A message was not delivered
Diagnose an undelivered message in order: consent, sender, template, window, handset, carrier.
Consent and opt-in
How consent is captured, stored per channel and purpose, and enforced automatically at send time.
Run a campaign
Segment an audience, choose a template, schedule the send and read the results without breaching consent.