Connect and validate WhatsApp

Choose the connection mode first

Open Settings → WhatsApp → Add WhatsApp sender. WRKZY offers two Meta Embedded Signup paths:

• Connect Business App: choose supported business-app coexistence when the business needs to keep using the WhatsApp Business App while WRKZY syncs supported activity.
• Connect Cloud API: choose a new or unused sender for WhatsApp Cloud API without existing Business App continuity.

Choosing the wrong path can disrupt the operating assumption for the number. Confirm how the business uses it today before starting Meta authorization.

Meta remains the authority for account eligibility and acceptable business messaging. Review the current WhatsApp Business Messaging Policy before connecting a production sender or changing how it is used.

Prepare the business and routing decision

1. Confirm the WRKZY workspace URL.
2. Confirm the Meta business and WhatsApp Business Account that own the number.
3. Identify the person authorized to approve Meta Embedded Signup.
4. Decide whether this will be the default outbound sender when several numbers are connected.
5. Choose the destination team inbox and the member group responsible for inbound work.
6. Record the current number usage and a rollback contact.
7. Prepare an approved external test number that can both send and receive.

Complete Meta Embedded Signup

1. Select the mode that matches the number.
2. Choose Connect Business App or Connect Cloud API.
3. Complete Meta's business, account, and phone-number selections.
4. Confirm the connection inside Meta when prompted.
5. Return to WRKZY and wait for the sender to appear in WhatsApp senders.
6. Open sender details and verify the displayed name/identifier, connection type, and status.
7. When more than one sender exists, select Set default only after confirming which identity should route ordinary outbound messages.

Meta Embedded Signup requires HTTPS. Local HTTP setup can show a message directing administrators to a deployed URL or HTTPS tunnel.

Read connection and sync state

History synchronization and new-message transport are related but not identical. A sync warning does not automatically prove inbound or outbound messaging is down.

Route the sender to Work

1. Open Settings → Messaging → Team inboxes.
2. Select the responsibility-owned inbox.
3. Attach or route the connected WhatsApp sender.
4. Confirm members, default/fallback routing, and any separate SLA or policy.
5. Review the channel count and explicit-route summary.

Open full size

Validate the customer path

1. From the approved external test number, send a unique harmless message to the connected business number.
2. Confirm a conversation appears in Inbox → Work under the expected team inbox and WhatsApp channel label.
3. Verify the customer/test contact and connected sender identity.
4. Assign the conversation.
5. Send a reply that complies with the current WhatsApp conversation/template requirements shown by the product.
6. Confirm the message changes from Sending to Sent and then any provider-reported Delivered/Read state.
7. Verify the reply arrives on the external device.

If validation fails

• Embedded Signup unavailable: preserve the exact visible message and contact WRKZY Support. Do not enter provider data in a workaround form or share Meta credentials.
• Meta returns no account or phone ID: restart only after the business owner confirms the correct WABA and registered number.
• Connected, no inbound message: verify the exact number, Meta callback subscription, sender status, and team-inbox route.
• Inbound works, outbound fails: verify default sender, recipient eligibility/restriction, allowed message type/template, and the visible error.
• Wrong team inbox: correct the channel route; do not rely on permanent manual reassignment.
• History sync failed: test new inbound/outbound separately, then recover the sync problem without removing a working sender.
• First reply is unclear: inspect message state before retrying to avoid duplicates.

Removing a number is consequential. It can stop future use in WRKZY; resolve exact target and continuity before confirming removal.

Measurable readiness

Track percentage of inbound tests routed correctly, unassigned WhatsApp work, send failures by reason, and time from provider failure to recovery. “Connected” is a setup milestone; correctly routed and verified customer communication is the outcome.