Stravax Engage keeps one contact book per organization. Contacts are created automatically from inbound WhatsApp conversations and web form submissions, or added in bulk through CSV import. Each contact carries a phone number, a name, custom field values your team defines, and any tags you apply, all scoped to your organization only.
Contacts enter your book from three places:
Every contact belongs to one organization. Your team can only see and search contacts inside your own organization, never another tenant's.
| Field | What it holds |
|---|---|
| Phone number | Normalized to one consistent format, so an imported contact and a contact from an inbound conversation match as the same person |
| Name | The contact's display name |
| Custom fields | Values from the field definitions your organization has set up |
| Tags | Labels drawn from your organization's tag vocabulary |
| Marketing consent | Whether the contact has opted in to marketing messages, shown next to the contact |
Consent status is what segments and broadcast sends check before a marketing message goes out.
Custom fields let your organization define exactly what extra data it tracks, instead of relying on a fixed set of columns. A field definition applies either to contacts or to conversations, and has a label (what your team sees) and a type that controls what values it accepts:
| Type | Accepts |
|---|---|
| Text | A single line of text |
| Multi-line text | A list of text entries |
| Number | A numeric value |
| Switch | Yes or no |
| Picklist | One option from a fixed list you define |
| User | One of your organization's team members |
Field definitions are a closed vocabulary, enforced on the server. Once a field exists, every value written to it, whether from the contact editor, CSV import, or elsewhere, is checked against its type. A picklist field rejects a value that isn't one of its defined options; a switch field rejects anything that isn't yes or no; an unrecognized field key is rejected outright rather than stored as loose data.
Tags are short labels you define once for your organization, then apply to any contact. Like custom fields, tags come from a fixed vocabulary you manage. An unrecognized tag is rejected rather than silently created, which keeps your tag list from drifting into duplicates and near-duplicates over time.
Contacts are plan-included up to a hard ceiling on your stored contact count, with an in-app upgrade path if you need more. See current plans for details.