SIXIS BUSINESS
OPERATIONS Discover SIXIS SOLUTIONS

Automated follow-up.Follow up whenit makes sense.

SIXIS sets up follow-ups after first contact, a conversation or a quote. Messages and tasks follow clear rules and stop when the situation changes.

The next action no longer depends only on the memory of a colleague. The team sees who returns and when, and the customer receives messages appropriate to the discussion, under the established contact conditions.

Tell us what remains unanswered See how we work

The discussion has begun.
Who comes back?

For teams that have conversations and deals in the works, with recognizable return moments and enough repetitive activities that their organization is worth automating.

  1. The offer has been sent and no one comes back.

    Each colleague follows the deadlines in his own way, and some proposals remain without continuation. We determine an action after the offer and how it becomes visible to the responsible.

  2. Messages continue after the client has responded.

    An automatic series does not know in time that the discussion has advanced or ended. We define the signals that stop or change the return and test how they get into the system.

  3. The promise to return does not turn into an obligation.

    The client says "we will discuss after the budget is approved", but the date remains only in the email. We link the agreed time to a task and the context that the colleague must have then.

A reason for return.
A rule of stopping.

Automation must recognize when it is time for a human to continue the conversation.

We start with clear business situations and choose whether an internal message or notification is appropriate. SIXIS configures and monitors the functionality included in the collaboration; you approve the commercial texts and rules.

The SIXIS collaboration model

  1. We choose the moments that demand a continuation.

    We identify situations such as the offer sent, the information promised or a return requested by the customer. We define which event triggers the next action and which data is required. We do not apply the same series of messages to all contacts in the system.

    From you Examples of conversations, terms used and situations in which the team must return.

  2. We determine the appropriate message or task.

    Some cases may receive an approved message; others require the person in charge to check the context before writing. We choose the intervals, the limited number of follow-ups and the contact conditions. A message refers to the actual offer or conversation and a useful step.

    From you Approved texts, commercial pace and who can answer questions that arise.

  3. We define estoppel and exceptions.

    We determine what happens in response, refusal, request to stop, acceptance of the offer or change of term. We check if the system can recognize these events. If it can't, we use a human check or an internal notification before a new message.

    From you Signals available in applications and the person who can decide unclear cases.

  4. We configure and test the entire route.

    We check the start, addressee, message data, interval and stop. We also test the response before returning, a changed offer or missing information. Connections between applications are practically confirmed before the flow is used with real clients.

    From you Required access and approval of tests and rules prior to activation.

  5. We follow what remains to be done.

    We see scheduled follow-ups, stopped messages, and tasks that need a human. Within established limits, we check operation and adjust cases that produce inappropriate follow-ups. The commercial result is tracked separately from the simple execution of a task.

    From you Feedback from discussions and confirmation of offer or process changes.

A WORKING EXAMPLE

The offer is under analysis.
The return takes into account of response.

A service firm sends a proposal and the client says they can discuss it after an internal meeting. In this example, the return has an agreed deadline and a person in charge, not just a fixed delay after the document is sent.

The established moment
We note the date and reason for the return. The manager receives a task with the offer and the context of the discussion, so that he can check the situation before contacting the customer.
An earlier answer
If questions arise before the deadline, the scheduled return is stopped or changed. The conversation continues with the requested information, through the designated person.
A change of decision
If the project is postponed or refused, we do not continue the same series. We update the status and determine if there is still a good reason and time to contact.

RELATED CAPABILITIES

Reversion uses the context of the sale.

A good follow-up depends on the information in the discussion and the current stage. Automation executes the rules; the commercial process gives them meaning.

When we start and when we stop.

Automatic messages, tasks for humans, and signals that change continuation.

Should all follow-ups be sent automatically?

No. An internal notification may be more appropriate when a verification or personal discussion is required. We choose what is sent automatically and what becomes the responsibility of the person in charge. The goal is appropriate continuity, not automation of every commercial message.

How do messages stop when the client replies?

We check where the response goes and if applications can safely transmit this change. We set the stop rule and test it before activation. If the response cannot be reliably detected, we do not claim that the shutdown is automatic; we use human verification or internal tasks.

After how many days should we return?

It depends on what was discussed, the offer and the client's term. A time agreed upon in the conversation takes precedence over a general interval. We set rules for repeated situations and a limited number of follow-ups, with the possibility of adjustment when new context arises.

Can we have different follow-ups according to the type of offer?

Yes, if the information and rules are clear. A standard proposal and a project seeking approvals may have different continuations. We keep differences that help the team work, without building dozens of hard-to-maintain variants. Texts and conditions are approved in advance.

What happens if a colleague contacts the customer manually?

We define how that contact is recorded and how it changes scheduled actions. The manager must be able to stop or move a return when the discussion has progressed. We check this situation in the system used, so that the manual contact and the automatic message do not continue independently.

Do we need a new application?

We first check the functions available in the current systems and what events can be tracked. We choose a solution according to requirements and real access, without an imposed provider. Any additional licenses, connections or configurations are specified beforehand; we do not promise that every application can support every rule.

Who checks that the automation works over time?

Collaboration specifies who monitors messages, errors, and unexecuted tasks and how much monitoring is included. SIXIS can manage the agreed verification, and a responsible person from your company confirms the commercial changes. We do not treat initial activation as proof that the process will work without maintenance.

What do we aim for as a result and what goes into the cost?

We check if the right follow-ups execute and stop correctly, if the tasks have a responsible, and which discussions continue. The cost depends on the situations included, the systems involved, testing and operation. We separate the costs of applications or messages; we do not guarantee acceptance of offers or a number of responses.

What discussions are worth a comeback?

Tell us what happens after the contact or after the offer and how the deadlines are now tracked. We can decide together where an automated message would help and where a human is needed.

Get in touch Back to Solutions