Platform / Task Automation
Task Automation

Task automation

Task automation on Palmate runs repeat work, such as order lookups, record creation and notifications, using rules you define. You set the steps, the connected systems and where a person must approve. The platform acts only within those permissions, so your team can see what’s happened at every step.

See what it can do
A customer using his phone to get help with a delivery
Customer

My item arrived damaged. Can you help?

Palmate

Could you share your order number and a photo of the item? I can use them to create a support request.

A support request is created and sent to the right team.

What does task automation do?

It stops your team from doing the same steps one by one. A customer asks about a damaged item, and Palmate asks for the order number and a photo, then creates a support request and sends it to the right team. Your team follows what’s been done instead of typing it in themselves.

01

Finds information

It gets order, customer or booking details from a connected system before it acts.

02

Creates or updates records

It opens a request or updates fields in systems you authorize, without manual re-entry.

03

Notifies people at the right time

When a defined event happens, it alerts the right person or starts a follow-up step.

04

Chooses a step based on the request

Within your allowed options, it can ask for details, take an action or bring in your team.

How does task automation handle a request?

A damaged item report shouldn’t always trigger the same action. Palmate checks the information first, then chooses the step you allowed for that case.

Customer: “My item arrived damaged.”

01

If details are missing

Ask the customer for the missing order number or photo.

The action waits until those details arrive.

02

If the details are complete

Create a support request in the connected system and assign it to the right team.

Let the customer know their request has been received.

03

If a person must approve

Send the return or replacement decision to a team member.

Continue according to your rule once approval comes through.

You might allow support requests to be created automatically while keeping refunds subject to staff approval.

YOU STAY IN CONTROL

Why stay in control of task automation?

You decide what starts a task, which details it needs and when human approval is required. Palmate acts only through connected systems and within the permissions you give it, so a request like "my item arrived damaged" still ends with a person confirming the outcome when you require it.

Customer

My item arrived damaged. Can you help?

Palmate

Could you share your order number and a photo of the item? I can use them to create a support request.

Channels and Integrations
GETTING STARTED

How do you get started with task automation?

  1. 01

    Choose a repeat task

    Write down what starts it and what should happen when it finishes.

  2. 02

    Define steps and limits

    Pick the required details, connected systems and the actions that need a person’s approval.

  3. 03

    Try different situations

    Check missing information, pending approvals and connection problems together before it goes live.

What should you bring to a task automation demo?

  • One task with a clear starting point and outcome
  • The systems used and the person who manages their connections
  • Allowed actions and the staff member who approves exceptions

Frequently asked questions

Do we have to write code for task automation?

No, most tasks can be set up by arranging steps visually. A custom connection to an unusual system may still need technical work.

Which systems can task automation connect to?

It works through ready-made connections and systems that allow data sharing. Palmate reviews your systems and the actions you need during setup.

Does task automation make every decision itself?

No, you choose its tasks and its decision limits. Steps that need approval go to a member of your team before anything changes.

What can start a task?

A customer message, a scheduled time or an event in a connected system can start a task. You and Palmate choose the trigger together during setup.

What happens if a connected system is unavailable?

Palmate follows the handling rule you defined during setup, such as routing the task to your team. Setup also covers what to tell the customer when an action hasn’t completed.

Can approval requirements differ by action?

Yes, you can let some actions run without review while others always wait for a person. Support requests might be created automatically, for example, while refunds stay subject to staff approval.

See how it works in your business.

A short demo can run on your own customer question or task, using the order lookups, record creation and notification steps described above.

Compare plans and usage on the pricing page, and use the demo to confirm which channels and connections your setup needs.