Omnique

The home page opens with the promise of never losing the number again, shows the connection in three steps and carries a price calculator, frequently asked questions and the Meta partner badge. Sign up accepts Google login and has bot protection. Whoever joins gets fourteen days with one instance, no card.

Four cards at the top: connected instances with the free slots, webhooks processed in the last 24 hours, forwarding failures and active subscriptions. Below, the volume chart for the last seven days, a summary with delivery rate, average latency and next charge, and the table of instances with status and number quality. The first steps block stays there until the four steps are done and then disappears.

The person clicks connect, chooses WhatsApp or Instagram, gives it a name and decides between keeping the number already in use on the phone app or connecting a new number. Meta's official window opens and, on return, the instance shows up with its state: connected, under review by Meta, needs reauthorisation, permission error or awaiting payment. When the slots run out, the same button leads to buying a slot.

Inside the instance, the webhook tab asks for the URL of the client's system and has a test button, which shows the response received right there. A switch turns forwarding on and off, the secret that signs each delivery can be replaced by a new one when needed, and a counter of consecutive failures sits on the same screen.

A tab inside the instance lists every event with date, type, status delivered, failed or pending, response code, latency and attempt number. Clicking the row opens the detail in a dialog, with phone and text masked by default and the option to see the full content.

A card in the webhook tab gathers whatever exhausted the five delivery attempts. The person inspects the event and resends it with the original content in one click, without asking Meta to send it again.

A card above the instance tabs lists the keys, several per instance, each with a label, separate permissions to send messages, send files, download received files and manage the account on Meta, a list of allowed addresses and last use. A revoked key keeps showing during the grace period.

In the connections list, the instance menu opens the dialog to connect Chatwoot, which asks for the address, the account and the token and creates the inbox on its own or uses an existing one. Once the connection exists, the test button appears. A received message becomes a conversation there, the agent's reply goes out through WhatsApp, with audio, video and files handled.

29 sections inside the panel: connecting, API key, the 24 hour rule, message templates, Meta costs, sending messages, sending without duplicates, files, webhooks, subscription, n8n, events, account management and Instagram.

Paid and used slots, monthly amount and next charge. Plans by the month, by the year or for 24 months, list of instances, invoices and notices of scheduled cancellation or declined payment. The card stays saved once registered. Card billing in Brazil, with international payment when enabled.

In the user's own account: referral code, commission plan, available credit and withdrawal history.

The widget at the top opens a ticket with an attachment, and the tickets page keeps the conversation. Verification in two steps through an app. On first access, a list of four steps to get started and a guided tour through connecting, key, logs and webhook, which can be replayed later.