SAC 360º - How to Configure and Manage Meetings

The 360º CS from SprintHub allows centralizing customer relations, integrating support, histories and meetings in one place. In this article, you learn how to configure, manage and track meetings, ensuring organization, productivity and a complete view of the customer.

---

Meetings in the 360º CS work as structured records of scheduled interactions with the customer. They are linked to the contact/lead and allow:

• Record date, time and responsible parties

• Set meeting status and type

• Centralize history and notes

• Track results and next steps

All of this integrated with support, without losing context.

---

How to Configure Meetings in 360º CS

1. Accessing the Meetings area

To configure and schedule a meeting in 360º CS, follow the step-by-step below:

1. Access the SprintHub

2. Enter the General >> 360º CS

3. Select the contact or support desired

4. Click on Meetings or Add meeting

5. Choose the calendar and click on Generate link

After generating the meeting link, the system provides three sending options:

• Copy link: copy the link and paste it directly into the support thread for manual sending to the customer

• Send with SprintHub standard text: the system automatically sends the message with a standard text

• Schedule as Contact: schedules the meeting by linking it directly to the selected contact

💡 This flexibility allows adapting the sending according to your team's support flow.

On this same screen, you can also:

• View already scheduled meetings

• Check if there was attendance or no-show

• Update the meeting status if it was not held

This ensures complete control of the customer's interaction history.

---

Best Practices for Using Meetings in 360º CS

• Record all meetings, even the short ones

• Update the status after it takes place

• Use notes to record decisions and next steps

• Standardize meeting titles and types

• Use reports for periodic analysis

---

Conclusion

With the 360º CS from SprintHub, meeting management ceases to be decentralized and becomes part of a single customer history. This ensures more organization, visibility and efficiency in support.