360connect · Automation & Integration

Automate the next step.
Keep your team in control.

Connect customer actions to the records, responses and team tasks that should follow.

Use supported forms, rules and workflow tools first. Scope a Connector when the journey needs an external system or new business logic.

Explore the journeys ↓Explore 360connect →
One enquiry · A connected next step
Customer · WhatsApp

“Can I arrange a visit?”

  1. Capture the requestContact + requirement
  2. Route the next actionAgreed team + process
  3. Continue the journeyConfirmation + follow-up record

Illustrative flow · Configured around the agreed scope

The workflow sequence

From a trigger
to a traceable outcome.

  1. 01

    Connect

    Receive an event from WhatsApp, a form or an approved system.

  2. 02

    Capture

    Create or update the relevant contact, submission or task record.

  3. 03

    Route

    Apply the agreed rule, review or human hand-off.

  4. 04

    Execute

    Run the supported action or separately implemented journey.

  5. 05

    Notify

    Issue the configured acknowledgement, update or team notification.

  6. 06

    Measure

    Retain the available status, activity and outcome records.

Practical starting points

Choose the process
you want to improve.

Enquiry workflow

Enquiry → qualified next step

Capture the requirement, answer approved questions and move the enquiry to the relevant team process.

Registration workflow

Form → confirmation

Capture required fields, record the submission and send an acknowledgement or review request.

Connected operations

Status change → update

Connect a supported business event to an approved customer notification or internal action.

These are implementation patterns. A client’s workflow is confirmed after reviewing modules, systems, permissions and timing requirements.

Structured intake

Start with the
information you need.

360connect · Supplied Smart Form Builder interface

A useful form gives the workflow something reliable to act on.

  • Agree the fields, supporting documents and consent requirements.
  • Define which submissions need a person to review them.
  • Connect the response, reference or next action to the submitted record.

Form configuration, notifications and any external data exchange follow the approved scope.

AI + rules + people

Decide where automation
should stop.

Rules & actions

Use a defined path.

Approved rules and configured actions handle known requirements and predictable decisions.

AI assistance

Understand within the scope.

When activated, AI can interpret an enquiry, use approved Knowledge or suggest a staff reply.

Human review

Keep judgement with the team.

Escalate unclear requests, exceptions and decisions that need a person. Review proposed Rule or Knowledge changes before use.

Related actual work

Registration connected
to operational review.

Tianma Charity Fair · Published event website reference

Tianma Charity Fair

Participant details, payment proof, organiser review, participant references and WhatsApp updates form one related event-system project.

This reference demonstrates custom system work. Its complete feature set is separately implemented and is not included automatically with a 360connect subscription.

View the project →
Agree before building

A workflow your team
can use and maintain.

  1. 01

    Map

    Trigger, fields, matching, decisions, timing and human responsibilities.

  2. 02

    Scope

    Supported configuration, new development, access and external service costs.

  3. 03

    Validate

    Test successful, incomplete, duplicate and rejected submissions as applicable.

  4. 04

    Operate

    Agree the acceptance criteria, team handover, support and change process.

Useful details

Before we begin.

Is a custom Connector included in a platform Plan?

A subscription provides the selected platform features. Connector development, new journeys, advanced integrations and material process changes require an agreed implementation scope.

Can every delay or follow-up sequence be configured immediately?

Supported scheduled tools and bespoke per-contact timing have different requirements. New state handling or timed journeys may require additional development and testing.

Does API integration mean native Official WhatsApp Cloud API is ready?

These are separate capabilities. Business-system integration is reviewed for the selected interface; native Official WhatsApp Cloud API support in 360connect remains on the product roadmap.

What reporting will we receive?

Records and reports reflect the fields, events and outcomes actually captured. Bespoke dashboards and external attribution are agreed as part of the implementation.

Connected services

Bring the workflow
into the wider campaign.

360connect Business Solutions→Shared conversations, customer context and everyday operations.GoWhere Campaign Pages→A mobile destination for action, lead capture and source-linked reporting.
Let’s work through it

Show us the process.
We’ll map the next step.

Share the trigger, systems involved and desired outcome. We’ll identify the supported tools and any implementation work.

Discuss my workflow ↗Send a brief →

Project reference