> For the complete documentation index, see [llms.txt](https://help.getswimtech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getswimtech.com/documentation/working-smarter-with-swimtech/the-power-of-messaging.md). # The Power of Messaging Discover how SwimTech Messaging helps your team communicate with customers from within the workflow, reuse consistent messages, and keep customer communication connected to the work being performed. **Customer communication should not require leaving the work you are already doing.** SwimTech brings communication directly into the operational workflow. Technicians and office personnel can communicate from the areas where they are already working, send an **Email or Text message to one recipient or multiple recipients**, and reuse established company communications instead of repeatedly creating the same messages. > **Create once. Communicate in context. Review communication.** ## One Connected Communication Workflow ### Message Templates - Create Once Many customer communications are the same or similar. **Message Templates** let your company create frequently used communications once and reuse them throughout SwimTech. SwimTech supports **unlimited Message Templates**, so the communication library can grow with the business. ### Messaging - Communicate in Context **Messaging** puts Email and Text communication into the SwimTech workflow. Users can communicate with a single recipient or multiple recipients without manually rebuilding recipient lists outside the application. Messaging is available from **Contacts, Quotes, Work Orders, Users, Fleet Management, a Technician's Daily Schedule, and a Technician's Route**. ### Message Log - Review Communication The **Message Log** provides a central area for reviewing Messaging activity, helping keep communication visible as part of the operational workflow. ## The Power of Operational Context One of the most useful aspects of SwimTech Messaging is that the people you need to communicate with can already be associated with the work you are viewing. * **One Contact -> Message that Contact** * **Multiple Contacts -> Message the selected Contacts** * **One Customer on today's schedule -> Message that Customer** * **All Customers scheduled for a Technician today -> Message the group** * **One Customer on a Technician's Route -> Message that Customer** * **All Customers on the Technician's Route -> Message the group** ## A Real-World Example Imagine that weather or another unexpected condition delays a Technician's Route. Instead of locating each Customer separately and repeatedly creating the same communication, SwimTech allows the user to work from the Route, communicate with the appropriate Customers, and use an established Message Template when one is available. ## Standardize What Is Repeatable. Personalize What Is Unique. Templates give the team a consistent starting point without forcing every communication to be identical. Users can begin with established wording and adjust the final message for the customer or situation. This can reduce repetitive typing, improve consistency, simplify training, reduce omissions, and keep customer communication relevant and personal. ## From Work to Communication Without Breaking the Workflow **Message Templates -> Messaging -> Message Log** **Create reusable communication -> Send it to the right recipient or group -> Review communication activity** > **The power of SwimTech Messaging is making customer communication a natural part of running the service business - from creating the message to communicating in context and reviewing communication activity.** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.getswimtech.com/documentation/working-smarter-with-swimtech/the-power-of-messaging.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.