Sales outreach approvals and compliance

Remy can prepare outreach, but your organization remains responsible for recipients, claims, consent, and applicable communication rules.

Prepare a prospect#

Open Sales, then Prospects or Pipeline. Confirm the person's name, company, role, contact address, source, and qualification evidence.

Do not treat an AI guess as a verified personal fact. Remove or correct data that cannot be supported.

Draft outreach#

Open Outreach and ask for a draft. State the purpose, sender, audience, tone, offer, maximum length, and call to action.

Use the Sales Playbook for approved targeting notes, message length, ask wording, and sequence guidance. Review the playbook when the offer or rules change.

Review the message#

Before approval, check:

• The exact recipient and channel
• Sender identity and reply address
• Company and personalization facts
• Offer, price, claims, and dates
• Links and attachments
• Suppression, opt-out, and consent requirements
• Local laws and company policy

A good message should make clear who is contacting the recipient and why.

Approve or reject#

Use Sales Approvals or the main Inbox.

Choose Approve only for the exact message and recipient shown. Choose Reject when it must not be sent. Add a reason so Remy can create a safer revision.

Some approval flows offer a revision path instead of a final rejection. Explain the required change without adding sensitive information.

Confirm delivery#

Approval changes the message state, but delivery is a separate step. A send can still fail because the recipient is missing, the channel is unavailable, the provider is not configured, or the provider rejects the request.

Read the final status. For an uncertain result, check the connected provider before sending again. This avoids duplicate outreach.

Manage sequences#

A sequence can schedule later work. Before starting one, review its steps and dates. Stop it when the prospect replies, opts out, is disqualified, or should not receive more messages.

Do not rely on automation alone for legal or suppression decisions.

Learn from outcomes#

Use Analytics, the Objection Library, Playbook, and Memory to record approved lessons. Separate measured outcomes from suggestions. Never store secret credentials or unnecessary personal data in memory.

Escalate safely#

For a disputed or sensitive message, stop the sequence and preserve the recipient, message ID, time, approval record, and provider result. Follow your organization's privacy and incident process.