Marketing Automation

Engage, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Engage account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Marketing Automation
  • Connects with a key
  • 22 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Engage is

Engage turns your customers into fans with personalised messaging; using emails, push and in-app notifications, and SMS.

You paste in a key from your own Engage account. It is kept encrypted, and you can withdraw it from inside Engage whenever you like.

How a run works

One message in, the work done in Engage.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Engage. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Engage account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

22 tools it already has

What it can do in Engage

These are the ready-made tools your AI employee already has in Engage. It is not limited to them, but it never has to be taught these.

  • Add Customer to AccountsTool to add a customer to one or more account entities. Use when you need to associate a user with accounts and optionally assign roles.
  • Add User to ListsTool to add a Customer or Account to one or more Lists in Engage.so. Use when you need to subscribe a user to specific lists for targeted messaging.
  • Archive ListTool to archive a List in Engage. Use when you want to prevent new subscribers from being added to a list. Existing subscribers will not be affected.
  • Archive UserTool to archive a user in Engage. Use when you need to deactivate a user account while preserving all historical data. The user will stop being active and all engagement and events
  • Batch RequestTool to batch multiple create user, update user, and add user events operations into a single API call. Use when you need to perform multiple operations efficiently at the cost of
  • Convert User TypeTool to convert a user between Customer and Account entity types. Use when you need to change a customer to an account or vice versa.
  • Create ListTool to create a new List in Engage for organizing subscribers. Use when you need to set up a new list for managing contacts or subscribers.
  • Create UserTool to create a new user (Customer or Account) in Engage. Use when you need to add a user with optional metadata, device tokens, or list subscriptions.
  • Delete Subscriber From ListTool to remove a subscriber from a List entirely (different from unsubscribing). Use when you need to completely delete a subscriber's association with a specific list.
  • Delete UserTool to completely delete all user data for a Customer or Account. This is a permanent, destructive action that removes all associated user data from Engage.
  • Get Account MembersTool to retrieve all members (Customers) of an Account in Engage. Use when you need to list users who are part of a specific account.
  • Get ListTool to retrieve a single List by its ID. Use when you need to fetch details about a specific List.
  • Get User By IDTool to retrieve a single user by their user ID. Use when you need to fetch complete user information including metadata, attributes, devices, lists, segments, and message statisti
  • List ListsTool to retrieve a paginated list of all Lists in Engage. Use when you need to view available Lists or iterate through all Lists in the account.
  • List UsersTool to retrieve a paginated list of all users in Engage. Use when you need to list users with optional filtering by email and cursor-based pagination support.
  • Merge UsersTool to merge two user profiles in Engage. The source user is merged into the destination user, and the source user profile is removed. Use when you need to consolidate duplicate u
  • Remove Customer from AccountTool to remove a Customer from an Account in Engage. Use when you need to disassociate a customer from a specific account.
  • Subscribe User to ListTool to create a user and subscribe them to an Engage.so List. Use when you need to add users to a specific list for email marketing or user segmentation. If the user already exist
  • Track User EventTool to add user events to Engage. Use this to track user actions and events in your application. You can later segment users based on these actions or events.
  • Update Account RoleTool to update the role of a Customer in an Account or set a new one if none exists. Use when you need to assign or change a customer's role within a specific account.
  • Update Subscriber StatusTool to update a subscriber's status on a List. Use when you need to subscribe, re-subscribe, or unsubscribe a user from a specific List.
  • Update UserTool to update user data and attributes on Engage. Use this to update user data changes like changes in plan, name, location, etc. If the user doesn't exist, this method creates th
Access, and who is in charge of it

You stay the boss of your Engage account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Engage account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Engage is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Engage and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

Questions people ask about Engage

Can an AI employee really work inside Engage?
Yes. It signs in to your own Engage account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Engage?
No. Nothing moves and nothing is replaced. Your records stay in Engage, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Engage account?
You paste in a key from your own Engage account. It is kept encrypted, and you can withdraw it from inside Engage whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Engage?
It has 22 ready-made tools in Engage today, among them Add Customer to Accounts, Add User to Lists and Archive List. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Engage and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Engage and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Engage?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Engage is written down with what it did and when.