Email Sending Service
Email from your team — Email connector notifications and the emails you send to respondents — goes out through your own sending services. RooQuiz does not relay it, so messages arrive from your own address.
Set them up under Settings → Team → Email Sending. Only the team owner and admins can manage sending services.
| Plan | Sending services per team |
|---|---|
| Free | 1 |
| Pro | Up to 3 |
Gmail accounts and SMTP servers share the same slots. Each Email connector then picks one of them under Sending service.
An email connector with no verified sending service still saves but never delivers. Its card shows a red "No sending service" tag.
Option 1: Connect Gmail (recommended for Gmail)
Click Connect Gmail and approve access in the Google window. There is no SMTP to configure and no app password — RooQuiz only gets permission to send email; it can't read your inbox.
- Each Gmail account sends up to 500 emails a day through RooQuiz. Bulk emails to respondents beyond that pause and continue automatically the next day; connector notifications beyond it fail until the next day.
- Test sends a message from the Gmail account to your own address.
- If the status shows Needs reconnecting, click Reconnect and approve again.
- To send from another Gmail address, connect another Gmail account.
Disconnecting deletes RooQuiz's access to that Gmail account. Turn off the email connectors that use it first.
Option 2: Add SMTP server
Click Add SMTP server to send through your provider's SMTP — useful for a brand domain via a service like Resend, or your company mail server.
What to fill in
| Field | Notes |
|---|---|
| SMTP server | Your provider's hostname, e.g. smtp.gmail.com |
| Port | 587 (STARTTLS), 465 (SSL/TLS) or 2525 |
| Username | Usually your full email address; some providers use a fixed literal |
| Password | The SMTP password or API key. When editing later, leave it blank to keep the stored one |
| From address | Must be an address your SMTP server is allowed to send as |
| From name | Display name shown to recipients |
| Reply-to | Optional, if replies should go somewhere else |
Port 25 cannot be used. Our hosting platform blocks outbound connections on that port. Use 587 or 465.
Provider setup
| Field | Value |
|---|---|
| SMTP server | smtp.resend.com |
| Port | 587 (STARTTLS) |
| Username | resend — the literal word |
| Password | A Resend API key (re_…) |
| From address | Any address on a domain you have verified in Resend |
This is the easiest option if you want notifications to come from your own brand domain rather than a personal mailbox, and it has no daily cap of the Gmail kind.
Save and verify
This section and the next apply to SMTP servers; a Gmail connection is verified by Google's sign-in.
Fill in the fields and click "Save and verify"
Saving and verifying are one action, so you never end up with a stored-but-untested configuration.
Check the inbox for the test email
The test email goes to your own RooQuiz account address — the one you are signed in with — not to the From address you just configured. If nothing arrives, check that inbox and its spam folder before changing anything.
Confirm the status reads "Verified"
Verified means your SMTP server accepted the message and returned a success code. That is not the same as delivered: an SMTP server accepts mail first and forwards it afterwards, so a message can still be filtered as spam or bounced later. If verification succeeds but nothing arrives, the problem is on the receiving side — start with the spam folder, then look for a bounce in the mailbox you are sending from.
When verification fails
The exact error from your SMTP server is shown on the page, deliberately unedited, so you can act on it directly. The common ones:
| Error | What it means |
|---|---|
535 Username and Password not accepted | Wrong credentials. For Gmail: you used the account password instead of an app password, or left spaces in it |
553 Sender address rejected: not owned by user | The From address isn't one this server may send as. Change it to a mailbox or alias the account actually owns |
550 relay not permitted | The server won't relay for you at all — usually the wrong username, or SMTP access not enabled on the mailbox |
| Timeout / connection failed | Wrong hostname or port, or the server doesn't accept connections from outside your network |
Good to know
- The password is never displayed again after saving. Leave the field blank when editing anything else, and it stays untouched.
- Changing the server, port, username, password or From address puts the status back to Not verified until the next successful check.
- Save and verify are rate limited to a handful of attempts per hour per team — each one really connects to your server and really sends a message.
- Removing the sending service deletes the stored password. You don't need to remove it to change settings — just save over them. Removal is refused while an enabled email connector still uses that sending service, so you can't silently break your own deliveries.
- If a later delivery fails permanently — the credentials stop working, or the From address is rejected — the status flips to Verification failed and email connectors stop delivering until you fix it. A single bad recipient address does not do this; it only fails that one message.
The Five Channels
The five connector channels — Email through your own SMTP, Webhook, Slack, Zapier and Kit — what each one delivers, the recipients and message format you can set, and one connector per channel.
Trigger Events & Scope
Every connector fires on trigger events and is limited by scope — which quizzes may fire it. What each of the five events means, how to narrow a connector to specific quizzes, and the consent filter.