What this messaging path is for
Vulcan Intelligence can prepare one editable SMS or email for an unambiguous recipient. The target can be an authorized contact, lead or thread, or an explicit phone number/email address you supply. A recipient does not need a newly created lead record merely to be addressed.
This is not a Gmail plugin, a bulk-mailing tool or a campaign enrollment action. Sender setup, permissions and the platform’s normal communication requirements still apply. This path does not support attaching generated files to a message automatically.
Resolve the destination first
- State the channel and the intended recipient.
- When using a name, inspect the returned contact choices. Choose explicitly if more than one matches.
- Check the actual destination and sender, not just the display name.
- Supply or review the message body and, for email, its subject.
Prepare wording without sending
Prepare an email to the customer on this selected estimate. Subject: Your generator estimate. Ask whether they have questions about the scope and invite a reply. Do not promise an installation date, add a discount or send it yet.
The editable draft should show the recipient and content. Correct it before confirmation. A general discussion of follow-up strategy is not permission to send; neither is selecting a person from search results.
A clear follow-up confirming the single pending draft can authorize the supported messaging path, but use the explicit action card when there is any ambiguity. Never approve a message whose actual address or text you have not checked.
Read the send result correctly
Drafted means the content is prepared. Accepted means the provider accepted the send, not that the recipient received or read it. Delivered is a provider-confirmed delivery state. If the outcome is unknown or still executing, inspect Message Center and the saved action before considering another send.
Do not repeat the request simply because the chat did not finish its response. A second send could duplicate the first one. Keep the action reference and refresh the saved status where offered.
Do not turn a helpful reply into an unsupported commitment
Use only approved prices, offers and timing. A message cannot reserve a real appointment merely by saying “you are booked.” Confirm scheduling in the appropriate booking workflow before promising it. Respect opt-outs and the requirements for the kind of message being sent.
For a multi-touch automated sequence, use Close Forge’s separate draft, readiness, publication and activation flow. For internal context, use an internal lead note instead of sending the note to the customer.
Working with a generated document
Create and inspect the PDF or Word document as a separate deliverable. The existence of a file card does not attach it to a message or publish it. Use a supported attachment workflow in the owning application rather than asking the assistant to pretend a link or attachment was sent.