1. Help
  2. Sera AI
  3. AI Automation Builder

No items found.
No items found.
  1. Help
  2. Sera AI
  3. AI Automation Builder

purple icon for coordination.
We’ve moved!
Our Help Center has a new home and our URLs have changed. Please update your bookmark to this page before April 30, 2026

AI Automation Builder

Build automation rules from natural language descriptions without writing code or pseudo code.

The AI Automation Builder allows specialists to create automation rules using natural language descriptions instead of manually configuring triggers, conditions, and actions. Sera AI interprets the description and generates a complete automation rule that the specialist can review and enable. Specialists do not need to be experts in script or code writing.

Creating an automation rule with AI

  1. Navigate to the Automation Rules section.
  2. Click to create a new automation rule. The Sera AI prompt is available in the rule editor.
  3. Describe what you want the rule to do in plain language. For example: "When a user says they can't send emails, classify the request as an incident."
  4. Run Sera AI. With that one natural language prompt, the automation is generated, including a trigger (for example, "On update of status"), conditions using pseudo code (for example, keyword matching or field value checks), actions to execute when conditions are met, and a description explaining what the rule does.

Review before enabling

Generated rules are disabled by default. The specialist must review the generated trigger, conditions, and actions, verify that the logic matches the intended behavior (at times you may need to make small tweaks to the pseudo code, but most things are pre-computed), and then enable the rule when satisfied.

This review step ensures that AI-generated rules do not take unintended actions.

Practical examples

  • Inbox management: "Complete low impact requests assigned to David Wood" generates a rule that triggers on status update, checks for low impact and the assigned person, and completes matching requests automatically.
  • Email classification: "When a user says they can't send emails, classify the request as an incident" generates a rule that classifies matching requests, applies the right SLA, and routes directly to the right team.
  • Kanban routing: "Anytime a request comes in for the content creation service, add it to the to-do column in my Agile board" generates a rule that automatically places new requests on a specific board.

The value extends beyond IT. Teams across the organization that use Xurrent for service management (marketing, facilities, HR) can build automations for scenarios they could not handle before, without needing technical expertise.

Best practices

  • Be specific in your description. More detail produces more accurate rules.
  • Review the generated conditions carefully, particularly for edge cases.
  • Test rules on a limited scope before enabling them broadly.