Platform / Task Automation
Task Automation

Task automation

Automation runs repeat tasks using rules you choose. Palmate finds order details, opens support tickets and sends updates. You decide which steps need approval from your team.

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?

When a customer reports a damaged item, Palmate asks for the order number and a photo. Once the details are complete, it opens a support ticket. It sends the ticket to the right team.

01

Finds information

Gets order, customer or booking details from a connected system. You choose the system and the information it can use.

02

Creates or updates records

Opens a support ticket once the details are complete. It can update records you give it permission to change.

03

Sends timely updates

For example, it can notify a customer when an order ships. You choose when to send a message and who receives it.

04

Chooses the next step

Asks for missing details. Starts the permitted task when the information is complete. Sends it to your team if approval is needed.

How does task automation handle a request?

The same request can need different steps. Palmate checks the details first. It chooses the next step using your rules.

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

Which tasks need approval?

You choose what starts the task and which information it uses. You also choose which steps need approval from your team. Palmate only carries out tasks you allow.

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 with ready-made connections or systems that can share information. A connection lets two software systems exchange information. We review your system and the tasks you need together.

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 time you choose or an order status change can start a task. We choose the method together.

What happens if a connected system is unavailable?

We agree on what happens if a connection fails. For example, the task can go to your team. We also test the response the customer receives.

Can approval requirements differ by action?

Your team sees completed steps and pending tasks on screen. Support tickets go to the right team member. Previous messages stay in one place.

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.