Email & inboxes
Planned messages, their purpose and the status of future connections.
This guide describes the planned workflow and what you can prepare today. These services are not yet enabled on this website.
Before you begin
- The Contact form and future inboxes are not connected yet. Account security messages use the existing studio service.
- Email templates exist in French and English. Their presence does not mean a message has been sent.
Step by step
- 01
Contact requests
Two messages are planned: an acknowledgement for the requester and a notification for the team. Acknowledgement must only be sent after the request has actually been recorded.
- 02
Account messages
The studio service handles verification codes, sign-in codes and password reset links. This website’s demo templates do not automatically replace messages sent by that service. Inbox invitations still need integration.
- 03
Future inboxes
The provider, sending domain, addresses and members must be configured before activation. An inbox invitation does not itself create an email address.
Practical example
Sales contact, support and data requests can have separate recipients. Final addresses will be published after activation.
Review checklist
- Status distinguishes drafts, recorded requests and provider-accepted mail.
- Replies must reach an inbox that is actually monitored.
- Addresses displayed in previews are examples.
Troubleshooting
Contact does not seem to send anything
That is the current behaviour: prepare, then copy or download your draft. No request is transmitted in the background.
A new inbox is needed
Prepare its purpose, owner and members. Creating it remains an operation for the future email provider.
Keep exploring
Still missing an answer?
Prepare a question for the team