Get help and contact WRKZY support

Start from the underlying record

A dashboard card, notification, or toast usually points to another record. Open the conversation, contact, import, campaign, quote, automation run, delivery event, or setting that produced the signal. Support can diagnose an observable state more effectively than a description such as “WRKZY is not working.”

Before changing anything, write down:

• the workspace slug;
• the feature and exact action attempted;
• the approximate time with timezone;
• the visible status or error text; and
• one safe record identifier from the URL when available.

Use the most specific guide

Search Help using the task and symptom together—for example, “WhatsApp connected no inbound,” “email reply failed,” or “import duplicate.” Follow the guide's verification and recovery steps once. Avoid broad changes such as reconnecting every provider, changing roles, or reimporting the same file until the first attempt is understood.

Isolate one reproducible case

1. Choose the smallest authorized test or affected record.
2. Confirm you are in the intended workspace and have the required role.
3. State the expected result in one sentence.
4. Repeat only a safe, non-duplicating action.
5. Record each step and the exact point where actual behavior diverges.
6. Inspect the relevant delivery state, history, execution log, notification, or session log.
7. Stop if another attempt could send a duplicate message, create a duplicate import, charge a customer, or overwrite configuration.

Build a useful support request

Use this structure:

Impact: Who is blocked and which customer outcome is at risk?
Workspace: Workspace name and slug; never include session data.
Expected: What should have happened?
Observed: Exact visible status or error.
Steps: The shortest sequence that reproduces it.
Time: Approximate timestamp and timezone.
Evidence: Safe record ID, provider event ID when explicitly shown for support, and a tightly cropped, redacted screenshot.
Recovery tried: One guide or action already attempted and its result.

Example: “At 14:20 IST, an approved test reply in workspace acme-retail remained Failed. Inbound messages still arrive. Conversation ID ends …28f1; Email delivery shows the connection needs attention. We followed the email delivery guide and did not retry to avoid duplication.”

Never send these items

Also remove unrelated customer names, message bodies, phone numbers, email addresses, attachments, and other tenants from screenshots. Crop to the status, control, or error being discussed.

Decide whether the issue is urgent

Escalate with clear impact when:

• customer communication is broadly failing;
• a security or privacy boundary may have been crossed;
• the same action may have created duplicate delivery or billing consequences;
• a workspace administrator cannot restore access; or
• a production workflow has no safe fallback.

For a suspected security or privacy event, stop experimenting, preserve evidence, and use the organization's approved incident route immediately.

After resolution

Confirm the original record reaches the expected state, not just that the error disappears. Record the cause and prevention in your team's operating notes. If the issue exposed a missing owner, test, routing rule, or monitoring step, update the launch checklist before expanding the workflow.