Frequently asked questions about SABSUS Cloud

Lead intake, order updates, payment reactions, notifications, status changes, internal tasks, content actions, webhooks and custom API logic.

Because embedded automation runs on the same live objects the team already uses, which reduces mapping gaps and sync errors.

Yes. CRM is not isolated. It can stay connected to orders, loyalty, communication and operating history.

Yes. The platform is role-based, so access and views can reflect the responsibilities of each team member.

No. It also connects to routing, order state, staff switching, taxes, tips, pickup, delivery and other operational logic.

Yes. The model supports multiple order types inside one order management flow.

Yes. APIs, webhooks, Flow actions and event-based logic are built into the architecture.

Yes. Payment integrations can be connected as part of the overall order and automation flow.

Yes. SABSUS Cloud supports branded customer-facing experiences and theme customization.

No. The goal is a branded experience on top of one connected operational core.

Not always. The migration can be phased, but the long-term goal should still be one connected architecture.

Map where customer identity, orders, catalog, payment state and manual work currently split between tools.