Skip to main content

Understand message templates, quick replies, and internal notes

BayEngine does not currently have a saved customer-message template or quick-reply library. Use the available document wording and place shop-only information in an internal note.

Write a normal message

  1. Open Inbox and the correct customer conversation.

    Open the correct conversation and write the message in the composer.

    Open the correct conversation and write the message in the composer.

  2. Confirm the phone number or email address.

  3. Write the message in the composer.

  4. Review the recipient and wording before sending.

There are no saved-message templates, placeholder menu, or quick-reply buttons in the Inbox today.

Use the wording included with customer documents

Sending an estimate or inspection starts with document-specific wording that you can review and edit for that send. BayEngine adds the portal link automatically. Editing the message does not save it as a reusable template.

Review the document message and portal-link delivery method before sending.

Review the document message and portal-link delivery method before sending.

Use reusable content for the right purpose

NeedUse
Repeatable labor, parts, fees, or service instructionsCanned service
A reusable inspection checklistInspection template
A repeatable staff follow-upAutomation and task wording
A customer text or email replyWrite or paste the message into the current conversation

Automation placeholders create staff tasks and notifications. They do not send customer messages.

Keep shop-only notes internal

  • Use repair-order or service internal notes for shop-only visit information.

    Record shop-only visit information in an internal note instead of customer-facing text.

    Record shop-only visit information in an internal note instead of customer-facing text.

  • Use customer or vehicle notes for information that should remain with that record.

  • Use findings and customer-facing service notes only for wording the customer should see.

  • Use a Task when someone needs to complete a future action.

What is not available yet

  • A shared message-template library
  • Quick-reply buttons
  • Customer-message placeholders
  • Internal conversation notes
  • Mentions inside a customer conversation