Forms & recipients

A form represents one form on your website — a contact form, a quote request, a careers application. Each form belongs to a site and carries three things:

• Recipients — who gets notified when someone submits
• Templates — what those notifications say
• Webhooks — optional delivery to a Slack or Microsoft Teams channel

Create one form per form on the page. If a site has a contact form and a newsletter signup, that is two forms — they almost always go to different people.

Create a form

1. Open Forms in the sidebar and click New form.
2. Choose the Site this form belongs to. Admins only — a manager with one site has it filled in already, and does not see this field.
3. Enter a Form key — the identifier the developer uses in their integration code, like contact-form.
4. Enter a Form name — the label you will see in the dashboard, like “Contact Form”.
5. Click Create. You land on the form detail page with four tabs: General, Recipients, Templates, Webhooks.

Give the developer both the site’s Site key and this form’s Key. Those two values are what identify the form when a submission arrives.

Add recipients

A recipient is one destination for one channel. A form can have as many as you need, and they can mix channels — the same submission can email two people and message a third on WhatsApp.

1. Open the Recipients tab and click Add recipient.
2. Pick the Channel. Every channel Expeed Relay supports is listed here whether or not the site can actually use it — the list does not reflect your site’s setup.
3. Enter the Address — an email address for the email channel, a phone number in international format for WhatsApp. One address per recipient: a comma-separated list is rejected, as is a Name <address> form. Add a second recipient instead.
4. Click Add. The recipient appears in the table immediately and applies to the next submission.

Screenshot to come

The Recipients tab of a form with the Add Recipient dialog open, showing Channel Type and Address

Confirm the site has a provider for the channel you picked. The Channel list is the same on every form — it shows what Expeed Relay supports, not what your site is configured for. Adding a WhatsApp recipient to a site with no WhatsApp provider is accepted without complaint, and then every delivery to that recipient fails. Check the site’s Providers tab first — see Configuring providers.

You can pause a recipient, but not edit its address. The table has four columns — Channel, Address, Active and Actions. Active is a switch: turn it off to stop notifying someone who is on leave, and back on when they return. The recipient keeps its place in the list either way, and paused recipients are skipped for new submissions.

Actions holds only a delete button — there is no pencil icon. To correct a typo in an address you still have to delete the recipient and add it back. Deleting is permanent, so note the address somewhere before you remove it.

Viewers see a status badge here rather than a switch, since they cannot change anything.

Each active recipient produces its own delivery job per submission. Three recipients means three jobs — and they succeed or fail independently, so one bad address does not stop the others. You can see them all on the Jobs page.

Templates

A template controls the wording of the notification. Open the Templates tab, click Add template, pick a Channel, and you get an editor with a Body. For the email channel you also get a Subject and an optional Footer; other channels have the body alone.

Templates support placeholders that are filled in from the submitted form data. A placeholder is the field name wrapped in double braces — if your form collects a field called name, then {{name}} in the template is replaced with what the visitor typed. A subject like New enquiry from {{name}} becomes “New enquiry from Priya Sharma” in the delivered email.

If you do not create a template, Expeed Relay sends a readable default containing the submitted fields. Templates are worth adding when you want a specific subject line, your own wording, or branding — not something you must do before going live.

The placeholder names must match the field names the developer used on the form. If a placeholder does not match anything in the submission it renders empty, so confirm the exact field names with whoever built the page.

Deactivating a form

The General tab has an active toggle. Turning a form off stops every notification it would have sent — including any delivery already queued but not yet sent — while leaving the form, its recipients, and its existing history intact. This is the safe way to retire a form on a page that is still live.

A deactivated form rejects browser submissions outright — nothing is stored. The visitor’s request comes back as the same generic 404 Submission target not found or not permitted a wrong key produces, and no submission row and no delivery jobs are created. So if you switch a form off while it is still on a live page, you stop capturing that data entirely rather than merely stopping the notifications. Take the form off the page first, or leave it active and remove its recipients instead.

Server-to-server calls made with an API key behave differently: the submission is still recorded, but unlinked from the form and with no delivery jobs.

Related

• Configuring providers — recipients can only use channels the site has a provider for
• Webhooks — send the same submission to Slack or Teams
• Submissions & jobs — confirm each recipient actually received it