SHVYA AI
Book a call ↗
☰
Features ↗Pricing ↗SHVYA Services ↗SHVYA Product Suite ↗Integrations ↗Documentation ↗ Blog ↗ Login
Skip to documentation content
SHVYA Docs Dashboard ↗
Go to workspace

Hosted WhatsApp and QR login

Pair a supported linked-device session and understand gateway health.

SHVYA product documentation

What Hosted means

Hosted uses a linked-device session handled by SHVYA's private WhatsApp gateway. Unlike the official Cloud API flow, it has browser-session pairing, QR refresh and account connection states. Session availability can affect live inbound, outgoing acknowledgements and background AI jobs.

  1. Open WhatsApp → Connect → Hosted.
  2. Create or select the session and choose Get QR.
  3. On your authorized WhatsApp device, open linked-device pairing and scan the QR.
  4. Check the session status until it reports a connected/ready state.
  5. Select View Chats, confirm the correct session and send an authorized test message.

Account controls

Depending on account state, SHVYA exposes View Chats, View Queue, Session Settings, Get QR / Refresh QR and Logout Session. An expired QR must be refreshed; a stale QR is not a successful connection.

Message delivery

The gateway needs a live connection, the private session state and its workers to complete sends. A locally queued message is not proof of provider acknowledgement. After a disconnect, messages may wait for controlled retries or require review if the provider outcome is uncertain.

When Hosted is delayed

  1. Check session status and account health before refreshing the whole dashboard.
  2. Verify a new inbound message arrives in the correct conversation.
  3. Inspect the latest message in View Queue rather than retrying it immediately.
  4. If QR continuously regenerates, recheck your linked-device pairing and session health.
  5. Capture the account/session ID and the affected message time; open a ticket.

Hosted troubleshooting · WhatsApp inbox.

Still need help with this?

Open a support ticket with the affected feature, what happened and a safe error reference.

Contact support ↗

More in Messaging Channels