Access your WhatsApp team inbox and integrations.
Your secure session ended. Previous workspace data has been cleared and background refresh has stopped.
Select the business you want to manage.
Your account is ready. Create your Interweb Connect workspace for this account and continue directly to WhatsApp setup.
This Lite release is designed for managed customer deployments. Requests are persisted in Supabase, attempted immediately where safe, and recovered by the five-minute cPanel cron worker.
Connect a WhatsApp Business Account, create a store-scoped credential, configure the WooCommerce plugin, and send a sandbox order event.
Presence, roles and account status for this isolated workspace.
| Agent | Role | Presence | Status | Last active |
|---|
Create a seven-day, single-use invitation link. The invited person must sign in with the same email address.
| Name | Role | Status | Expires |
|---|
Status, priority, assignment, note and membership actions. Message bodies and credentials are excluded.
| Time | Action | Target | Details |
|---|
Assignments, new messages, SLA alerts, billing reminders and WooCommerce failures.
These settings apply only to your agent account in this workspace.
Mandatory modules cannot be removed. Optional modules and quantities determine the new order.
| Module | Action | Qty | Recurring charge | Setup |
|---|---|---|---|---|
| Select modules to calculate the server quote. | ||||
Configure a bounded rule-based WhatsApp assistant. A human-owned conversation always takes precedence.
Rules run by priority. Exact and interactive reply IDs are evaluated before the fallback rule.
| Priority | Rule | Trigger | Response | Status |
|---|
Release a handed-off session only when the team wants automation to resume.
| Conversation | Reason | Handoff |
|---|
Sanitized rule outcomes; customer message bodies are not repeated here.
| Time | Outcome | Rule | Detail |
|---|
Tenant-scoped commerce assistance, published WhatsApp Forms/Flows, and appointment booking built on the certified deterministic bot and durable queue.
Answer order-status requests using authenticated order snapshots. Product, return and cancellation requests route safely to the human team.
The connector sends status snapshots only. Raw credentials and full webhook payloads are never displayed here.
| Order | Status | Total | Items | Updated |
|---|
| Type | Status | Summary | Created |
|---|
| Service | Duration | Status |
|---|
Scheduled times follow the configured appointment timezone.
| Scheduled time | Service | Status | Confirmation | Created |
|---|
| Scheduled time | Service | Status | Confirmation | Created |
|---|
Register an already published Meta Flow and use it as a deterministic bot-rule response.
nfm_reply. Encrypted dynamic endpoint/data-exchange flows remain outside this shared-hosting release.| Name | Flow ID | Status | Category |
|---|
| Received | Flow | Status | Fields |
|---|
Your active paid modules determine the recurring charge. Bundle names are references, not separate charges.
The forecast is informational until a renewal invoice is issued. A paid scheduled order remains pending until its effective date.
Pay the invoice through an approved local method, then submit the transaction reference and optional proof for verification.
Issued, paid and overdue subscription or service invoices.
| Invoice | Type | Status | Issued | Due | Total | Balance |
|---|
| Date | Invoice | Method / reference | Amount | Status | Proof / receipt |
|---|
Brand the customer-facing workspace, invoices and receipts for this tenant.
These details appear on printable invoices and receipts. Empty fields fall back to platform defaults where appropriate.
Checking connection status…
Cloud API messaging is enabled after phone registration and Meta accepts this app's WABA webhook subscription. Read-back confirmation may arrive later.
Messages sent from the mobile Business app or linked devices are mirrored through smb_message_echoes. Imported history is identified separately from live inbox traffic.
Send Meta's approved hello_world template from this workspace's connected number. Reply to that message from the recipient phone to validate the Team Inbox.
Stage the existing coexistence number under the verified Interweb Technologies portfolio. The current live connection is not replaced until all destination checks pass and you type the explicit cutover phrase.
Type PREPARE +number to create an encrypted staging attempt.
—, then create or select an Interweb Technologies-owned production WABA for the same phone number.Type the exact phrase shown below. These actions never unsubscribe the source WABA automatically.
—
The previously approved PHP Embedded Signup deployment remains available as an onboarding fallback. It must not be used to overwrite or disconnect the current certified coexistence connection during this controlled migration.
Open legacy onboardingEach WooCommerce store receives one revocable credential. The secret is displayed only once.
Use this API URL in the Interweb Connect WooCommerce plugin.
| Name | Store | Environment | Status | Last used |
|---|
Store registration, plugin version and last successful contact with Interweb Connect.
| Store | Versions | Status | Last seen | Last event |
|---|
Keep plugin-managed templates for backwards compatibility, configure templates centrally, or disable an event without changing the WordPress store.
| Event | Management | Template | Language | Category | Consent |
|---|
Operational history contains event type, store, delivery acceptance and sanitized failure codes. Customer payloads and credentials are not displayed.
| Time | Store | Event | Order / source | Status | Response |
|---|
Use this for a clinic, CRM or another trusted backend. The secret is displayed once and must remain outside browser and mobile code.
Copy the generated secret into the clinic backend’s private .env file.
VITE_, NEXT_PUBLIC_ or REACT_APP_ for this secret. React and Flutter must call the clinic backend, which then calls Interweb Connect.Each credential is tenant-scoped, client-bound, revocable and permission-limited.
| Name | Client ID | Environment | Permissions | Status | Last used |
|---|
GET /api/v1/external/ping
GET /api/v1/external/templates
POST /api/v1/external/contacts/upsert
POST /api/v1/external/messages/template
POST /api/v1/external/messages/text
GET /api/v1/external/messages/{message_id}
GET /api/v1/external/conversations?phone=923001234567
All requests require Authorization: Bearer … and X-IWC-Client-Id. Message POST requests also require a unique Idempotency-Key.
Confirm the itemized charges before creating the invoice.