AIBiz Emailer Help Center

What This App Does

• Sends one transactional email to one recipient at a time.
• Stores sender identities, reusable templates, and send history.
• Lets suite apps send approval links, account notices, reminders, and follow-ups through a protected suite connection.
• Tracks failures so staff can see when SMTP is not configured or a message could not be delivered.
• Provides a single place for suite apps to request email without each app managing its own SMTP settings.

What This App Is Not

• It is not a mass email marketing tool.
• It does not manage campaign lists or newsletter blasts.
• It does not replace campaigns.aibizshop.com.
• It does not guarantee delivery until a real sender account is configured on the server.
• It should not be used to send spam, cold blasts, or unapproved bulk outreach.

Recipient Email

Staff enters the customer email address when sending a message or when another app creates a message request.

Example recipient: customer@example.com

The customer provides the recipient email, but AIBizShop must provide and configure the sender email system.

Sender Email

The app sends from an approved AIBizShop sender such as billing@aibizshop.com, approvals@aibizshop.com, or emailer@aibizshop.com.

The server needs SMTP host, username, password, sender email, port, and security settings before automatic emails can leave the app.

If SMTP is missing, the app can still create the send record and show a failure so staff knows the sender is not connected yet.

Sender Identities

• Create a sender identity for each approved from-address staff may use.
• Use clear display names so customers recognize the business or department.
• Keep inactive or test senders disabled for production messages.
• Match sender identities to verified SMTP or domain settings before relying on delivery.

Templates

• Create templates for approval links, reminders, account notices, and simple follow-ups.
• Use variables only where the connected app is expected to provide real values.
• Keep subject lines direct and customer-friendly.
• Review template wording before connecting a suite app to automatic sends.

Send History

• Every attempted send should create a visible record.
• Sent means the configured mailer accepted the message.
• Failed means the app could not send through the configured service.
• Missing configuration means SMTP or sender settings still need to be completed.

Free Tier Flow

1. Confirm the email profile has the correct business name and default sender.
2. Add a sender identity for the address customers should see.
3. Create a reusable template when the same message is sent often.
4. Send one message to one recipient.
5. Check Send History for sent, failed, quota, or missing-configuration status.