Actito

actito.com ↗

Lifecycle scenarios with controlled repeat entry, entity boundaries and purchase exits

SI Score
75/100
Pricing
Contact for Pricing AI reading, not confirmed
Free plan
Not confirmed
Sign-up required
Required AI reading, not confirmed

Ask SI about Actito

Answers use saved listing facts and recorded sources.
Homepage screenshot
Screenshot of the Actito homepage

What it does

Actito builds customer messaging scenarios from triggers, filters, waits and actions. Teams use licensed user accounts, with access restricted by role and business entity. Its quoted Standard and Advanced offers cover different active-profile, seat and channel needs.

Choose the profile database and entity carefully when creating a scenario: those settings cannot be changed later, and the scenario can use resources only from the same entity. The default execution rule also matters. A new trigger is ignored while the same profile's current execution remains unfinished, unless another execution mode is selected.

A one-time welcome benefit can use one execution per profile. Repeated order-related messages may instead need concurrent executions or replacement of the existing one. Global exits can stop a cart-reminder scenario when a purchase appears in a linked Order interaction table, so that table and its incoming data must exist for the exit rule to work.

At a scheduled end, Finalise allows current executions to finish while refusing new ones; without it, running executions stop at the deadline. An activated scenario cannot be edited. Set the ending behaviour before activation alongside the paths and repeated-entry policy.

Standard covers up to 100,000 active profiles and 10 seats; Advanced covers up to 500,000 active profiles and unlimited seats. Request a quote for the channels and capacity needed. An administrator creates staff accounts under License configuration > Users and assigns both a rights configuration and an entity group. Give a campaign author access to the entity containing the relevant database and templates.

Strengths

  • Execution modes distinguish one-time, concurrent and replacement participation
  • Linked interaction data can stop reminders after the relevant purchase

Watch out for

  • The scenario's database and entity cannot be changed after creation
  • Activated scenarios cannot be edited

Best for

  • Lifecycle teams coordinating repeated customer events and linked-data exit rules

Sources