Understand Bilty WhatsApp recipient resolution
Understand verified CRM-conversation precedence, optional stored-phone conversation matching and why IP addresses are never used to infer a telephone number. The guide follows the Help Centre standard: exact route, prerequisites, ordered steps, verification and operational boundaries.
What you’ll accomplish
Understand verified CRM-conversation precedence, optional stored-phone conversation matching and why IP addresses are never used to infer a telephone number. Bilty Management keeps drafts, issued records, public capability links, finance, integration events and audit evidence as connected but separately verifiable records.
How the workflow fits together
Use the native Britixo WhatsApp bridge, event triggers, recipient resolution, templates and secure links. Use the module's current status, permission checks, warnings and linked records to decide the next supported action. Where a downstream invoice, WhatsApp queue item, webhook, PDF, POD record or audit event applies, verify it separately.
Follow these steps
- Go to Bilty Management → Settings → WhatsApp automation and open the relevant current record or configuration view.
- Review the displayed state and compare it with the explanation in this guide.
- Compare the live values with the workflow described in this guide: Understand verified CRM-conversation precedence, optional stored-phone conversation matching and why IP addresses are never used to infer a telephone number.
- Follow any linked record, status, public evidence, invoice, queue or audit entry rather than inferring that a downstream action happened.
- Use the related guides below for the operational action that changes the record.
Fields and decisions to review
Record, audit and evidence checks
Reopen the relevant Bilty record or register and confirm its identifier, current status, related parties, timestamps and connected evidence. Check the audit/compliance, payment, public-link, report, API, webhook or WhatsApp evidence that applies to this workflow rather than relying only on a success alert.
How to confirm it worked
Return to Bilty Management → Settings → WhatsApp automation or the resulting register and verify that the stored state matches the intended action. For any downstream automation, confirm the downstream record or queue/log entry as a separate completion check.
Technical basis for this guidance
This guide was checked against libraries/Bilty_whatsapp_bridge.php; models/Bilty_management_model.php; helpers/bilty_helper.php; views/admin/settings.php. It documents only behaviour exposed or enforced by the supplied module; internal secrets, raw signature payloads and unsupported future workflow assumptions are intentionally excluded.
Controls, checks and common mistakes
- Bilty does not store a second WhatsApp connector session or credential set.
- An IP address is never used to infer a customer telephone number.
- Real delivery/read status depends on the connected WhatsApp runtime and must be verified there.