Courier and Client Integrations

Guide intro

Courier integrations matter because they connect conversation workflows to downstream operations. But they should be treated carefully. A visible integration option does not automatically mean the workflow is ready for live use in every account or every business process.

This guide explains how to think about client-facing courier support responsibly, including what should be tested before relying on it for daily operations.

Supported versus coming soon

Client-facing materials should distinguish clearly between currently supported courier workflows and future plans. As reflected in the current public product information, some courier support is available while other integrations may still be described as coming soon.

That distinction matters because businesses need to know whether a workflow can be tested today or should only be treated as roadmap context.

Credentials, testing, and operational readiness

Even when a courier workflow is available, the business should confirm that the right credentials, field requirements, and internal order steps are ready. An integration is only operationally useful when the input data is clean enough for the courier flow to succeed.

Test with realistic sample orders before the workflow is trusted for regular customer traffic.

Best practices

• Validate order fields before depending on an integration path.
• Run controlled tests before enabling courier-dependent promises to customers.

How to talk about integrations carefully

Avoid describing a courier setup as fully production-ready unless your account and workflow have actually been tested end to end. The same principle applies to any public messaging about WhatsApp or third-party platform support: be precise, not optimistic.

Related docs