Glossary

This glossary defines the onboarding, Infobip, Meta, channel, GDPR and billing terms used across the Arino One documentation, so a term you meet in one article means the same thing everywhere else. It is organised alphabetically within each group below rather than as one long list, since most readers are looking up a term from a specific area of the docs.

Onboarding and platform terms

Arino Core — The Arino One platform itself, and the name of the optional $50/month connection taken after an instance is built.

Remix — The instance type (and onboarding route) for clients who do not yet have an Infobip account: you register on client.arino.one, confirm by OTP and email, then create your own Infobip account through Infobip's signup flow. It is also Lovable's term for copying the Arino One template into your own project, which is exactly what the Self-build option involves.

BYO (Bring Your Own) — The onboarding route for clients who already have an Infobip account. You register and confirm as normal, then connect your existing Infobip keys and continue paying Infobip directly.

Self-build — Build option 1, free. You (or your developer) remix the Arino One Lovable template into your own workspace and build the instance yourself. No Arino setup fee applies.

We build it for you — Build option 2, a flat $350 one-time fee. Arino sets the instance up on your behalf. The resulting instance is yours, as is the Infobip account behind it.

Arino Core connection — The optional $50/month connection taken after the instance is built, covering management, support, updates and access to WebRTC calling. Skipping it leaves you with a working instance that Arino does not support or manage.

Instance — Your dedicated, single-tenant Arino One deployment: console, database and channel connections.

Console — The operator interface for your instance, where channels, templates, contacts, campaigns and users are managed.

Infobip and Meta terms

Infobip — The messaging infrastructure provider Arino One connects to for WhatsApp, SMS, RCS and voice delivery. The Infobip account is always the client's own, on both routes.

API key — The credential that authenticates an instance against an Infobip account. These keys belong to the client in every case; Arino connects to them but never owns the account.

WABA — WhatsApp Business Account, the Meta object a phone number sender belongs to and the unit against which messaging tiers and quality ratings apply.

Messaging tier — The daily cap on unique WhatsApp recipients a WABA can message with business-initiated conversations, which rises automatically with sustained quality and volume.

Quality rating — Meta's green/yellow/red score for a WhatsApp sender, driven by recipient blocks and reports, which directly affects messaging tier and template availability.

Template — A pre-approved message format required for business-initiated sends on WhatsApp and RCS, submitted to Meta under a category (utility, authentication or marketing).

Conversation — A billing and threading unit; on WhatsApp this is a 24-hour, category-based window inside which any number of messages can pass. Charged by Meta and Infobip directly to the client.

Channel terms

Sender — The identity a message is sent from: a phone number, short code, alphanumeric ID or verified business account, depending on channel.

Live web chat — The embeddable chat widget on a client's own website, included free and unlimited with the $50/month Arino Core connection.

Ping Me — Arino's physical call-button device; a customer presses it to start a voice call through the instance, billed at $0.10 per press and $0.009 per talk minute on top of the $200 one-time device cost.

Voice / WebRTC — Browser- and app-based calling routed through the instance. WebRTC calls are billed at $0.009 per minute and are available only while the instance holds an active $50/month Arino Core connection; PSTN number rental and termination are paid directly to Infobip at your account rates.

Fallback — Automatic re-send on a second channel when the first channel cannot deliver a message.

KakaoTalk — South Korea's dominant messaging app, available through Infobip. Business-initiated sends use pre-registered Alimtalk templates tied to a Kakao business channel. See KakaoTalk.

Zalo — Vietnam's dominant messaging app, available through Infobip. Requires a verified Official Account, and business-initiated sends use ZNS templates. See Zalo.

Apple Messages for Business — Apple's business messaging channel, reached from entry points such as Maps, Safari and Siri. Always customer-initiated, and connected through a Messaging Service Provider. See Apple Messages for Business.

Carousel — A horizontally scrollable set of cards in a single message, each with its own media, text and buttons; built in the carousel builder and sent from the inbox or a campaign. See Carousels.

Location message — A map pin sent to, or received from, a contact — name, address and coordinates — captured against the contact record. See Location messages.

Short link / link tracking — A long URL rewritten as a first-party short link served by your own instance, so clicks are attributed to a contact and a campaign without a third-party shortener. See Short links and click tracking.

OTP (one-time passcode) — A short, single-use code sent over one of your channels to verify a phone number at login, checkout or another sensitive action; tracked as sent, verified or expired. See OTP and 2-factor verification.

Canonical contact name — The single display name Arino One settles on for a contact from the signals each channel provides, so the same person reads the same across the inbox and CDP. A manual override always wins. See Contact names across channels.

WhatsApp Payments / payment link — Taking payment for an order in the conversation: native in-chat payment in India (UPI) and Brazil, and a Stripe Payment Link everywhere else. See WhatsApp Payments.

GDPR and compliance terms

Data controller — The party that decides why and how personal data is processed. For customer data passing through an instance, this is normally the client.

Data processor — The party processing data on the controller's instructions; Arino One acts as processor for the client's customer data.

Consent record — A stored, timestamped record of a contact's opt-in, including source and wording shown, used as evidence for marketing sends.

Erasure request — A data-subject request to delete personal data, handled per the retention and erasure process for the instance.

Retention policy — The configured length of time message content, contacts and media are kept before automatic deletion.

Billing terms

Setup fee — A flat $350 one-time charge, payable only under the We build it for you option. Self-build carries no setup fee.

Connection fee — The optional flat $50/month Arino Core connection covering management, unlimited seats, unlimited live web chat, platform and GDPR features, support and access to WebRTC.

Usage / metered cost — Message and conversation charges. These are paid directly to Infobip and Meta by the client and are never billed or marked up by Arino.

AI — Text AI features (assisted replies, summarisation, translation) run either on Lovable AI, the managed default that needs no key and is metered in Lovable AI credits billed by Lovable, or on your own OpenAI or Anthropic key billed by that provider. ElevenLabs, configured separately, provides synthetic voice for greetings and voicemail. AI is always metered, Arino adds no markup, and it is not part of the $50/month connection. See AI features and your own API keys.

client.arino.one — The registration and billing portal where clients confirm their account and, if they hold Arino charges, view invoices and pay by card or Stripe.

Frequently asked