Contact
Route: /org/ecom/storesettings?tab=contact · Permission: Manage Store Settings
1. What Contact covers
Two different things that look like one, and confusing them is the single most common misconfiguration on this section:
| Group | Audience | Purpose |
|---|---|---|
| Contact Information | Customers | How shoppers reach the store |
| Transactional alerts | The store's own staff | Where order notifications land |
The placeholder text spells the distinction out: the notification email is "[email protected] — separate from public support email".
The support fields are shown to customers. The notification fields are not. If the same address is used for both, an internal alerts inbox becomes a public contact route — and it usually is not staffed for customer replies.
2. Where each field goes
3. The form
The WhatsApp verification state
The WhatsApp number carries a Verified / Unverified chip. Verification is not performed on this screen — the chip reports the state of the number in the organization's WhatsApp connection.
Nothing prevents saving an unverified number. It simply will not be usable for WhatsApp messaging until it is verified in the communication channel configuration.
4. Field reference
| Field | Control | Audience | Placeholder |
|---|---|---|---|
| WhatsApp Number | Text + verification chip | Customer | +91 88001 12233 |
| Support Phone | Text | Customer | +1 415 555 0190 |
| Support Email | Customer | [email protected] | |
| Notification Email | Internal | [email protected] — separate from public support email | |
| Notification WhatsApp | Text | Internal | +1 555 0142 — for transactional alerts |
| Physical Address | Textarea | Customer | Store address |
None of the six is enforced as required, and no format validation is applied on the section — an invalid phone number saves.
5. The admin contract
| Prerequisite | Without it |
|---|---|
| Manage Store Settings | Read-only |
| A verified WhatsApp connection | The WhatsApp number cannot actually send |
| A monitored ops inbox | Transactional alerts go nowhere useful |
6. Downstream
| Field | Consumer |
|---|---|
| Support phone, email, WhatsApp | The storefront's contact surfaces |
| Physical address | Storefront and invoices |
| Notification email / WhatsApp | Order and transactional alerts |
7. Don't confuse this with…
| Thing | Where | Why |
|---|---|---|
| Support email | Here | Public — customers see it |
| Notification email | Here | Internal — alerts only |
| Communication channels | Organization settings | Where WhatsApp and SMTP are actually connected |
| Storefront Support tickets | /org/ecom/support/tickets | Handling what customers send |
8. Troubleshooting
| Symptom | Cause |
|---|---|
| WhatsApp shows Unverified | The number is not verified in the WhatsApp connection |
| Customers email the ops inbox | The same address is in both groups |
| No order alerts arrive | Notification fields are empty, or the channel is not connected |
| A malformed number saved | The section does not validate formats |