Email & SMS

Workflows can notify people by email and SMS — for example, confirming a request was received, or letting a customer know their issue is resolved.

There are two ways to send, and you can mix them:

• Built-in sending (included) — send straight away using assess.one’s own email and SMS gateway. No setup, no provider account. Usage is covered by email and SMS credits included with your plan.
• Your own provider — connect AWS or Twilio and send from your own account. These sends are unmetered (they don’t use credits) and carry your sender identity, not assess.one’s.

Built-in credits are the fastest way to get started, but connecting your own provider is recommended for greater control — your own sender identity and branding, your deliverability and reputation, unmetered volume, and full visibility of sending in your provider’s console. Built-in sending is ideal for trying things out and lower volumes.

Included email & SMS credits

Every workspace includes a balance of email and SMS credits for built-in sending. One credit sends one message. Credits are a lifetime allowance — they’re granted once and do not reset each month.

Plan	Email credits	SMS credits
Free	20	5
Paid (any paid plan)	1,020	105

The first time you move to a paid plan, an extra 1,000 email and 100 SMS credits are added on top of your free allowance — once. Changing plans after that (up, down, or cancelling and re-subscribing) doesn’t grant more.

Note

Credits belong to the workspace, shared across everyone in it — not per user. They’re only used by messages sent through the built-in gateway inside your workflows. Sending through your own connected AWS or Twilio account never uses credits.

Checking your balance

Go to Settings → Integrations to see how much of your email and SMS credit you’ve used. Workspace admins are emailed automatically when usage reaches 80% and again at 100%, so a limit is never a surprise.

When credits run out

If you reach your limit on the built-in gateway, workflows keep running — the send step is simulated instead of failing. Nothing is sent, the record isn’t stranded, and the step is clearly marked in the activity timeline as “Simulated — No Email Credit” or “Simulated — No SMS Credit”.

To keep sending real messages after that, connect your own AWS or Twilio account (below). Own-provider sends are unmetered, so they continue regardless of your credit balance.

Built-in sender identity

Messages sent through the built-in gateway are sent on assess.one’s shared, reputation-managed gateway and are lightly branded — email arrives from “Your Workspace via assess.one” and includes a small by assess.one tag. When you send through your own AWS or Twilio account, messages use your identity with no assess.one branding.

Connecting your own provider

Connecting your own account is the recommended setup for ongoing use — it gives you unmetered volume, your own sender identity and number, and full control over deliverability and reporting.

• AWS — send email (via SES) and SMS (via SNS) under one connection.
• Twilio — send SMS.

You can connect more than one and pick a preferred provider per capability.

1. Go to Settings → Integrations and choose AWS or Twilio.
2. Enter the required credentials (for AWS, an access key and region; for Twilio, your account details and sending number).
3. assess.one validates them and shows any provider error directly, so you can fix issues immediately.
4. Use Send test message to send yourself a quick confirmation and prove delivery works.

Once a provider is connected and preferred for a capability, matching workflow sends go through your account and stop using credits.

How workflows use them

When your process description mentions notifying someone, assess.one adds email/SMS steps that send to the contact captured on the form — for example, the customer’s email or phone field. Recipients always come from the record’s data (an email or phone field), never a hard-coded address.

Tip

To reach a fixed internal contact (like an on-call manager) rather than the customer, model it as a task assigned to that role instead of a message — it’s more reliable and keeps an audit trail.

Troubleshooting

• A message didn’t send? Open the record’s activity timeline to see the status of each send step — including retries and any step marked Simulated. For a send that permanently failed after all retries, Settings → Logs records the failure with the provider’s reason.
• A step shows “Simulated”? You’ve used all your built-in credits for that channel. Connect your own AWS or Twilio account to keep sending, and check your balance under Settings → Integrations.
• Provider rejected the credentials? The error from the provider is shown when you connect or test, so you can correct the key, number, or region.

Next

• Payments →
• Integrations overview →