ServiFlow is a modern IT Service Management (ITSM) platform that helps your team manage support tickets, track SLAs, maintain a configuration database, build a knowledge base, and leverage AI to work smarter.
This guide covers everything you need to use ServiFlow day-to-day. It is written for three audiences:
ServiFlow offers a free trial so you can explore the platform before committing to a plan.
The login screen asks for three fields:
| Field | Description |
|---|---|
| Tenant Code | Your unique company identifier (e.g. acme). Provided in the welcome email. |
| Username | Your personal username. The first admin account is admin. |
| Password | Your password. Change it after first login. |
On your first login, ServiFlow offers a 15-step guided tour that highlights key areas of the interface, including the dashboard, navigation, ticket management, SLA setup, and integrations. You can restart the tour at any time by clicking the ? help button in the top navigation bar.
Click your profile icon in the top-right corner and select Change Password. Enter your current password and choose a new one.
After your first login, follow this checklist to configure ServiFlow for your organisation.
The admin dashboard gives you a bird's-eye view of your service desk operations. The sidebar uses collapsible sections to organise navigation, with sensitive settings behind an elevation-gated System Admin Tools section.
At the top of the dashboard, the Quick Admin panel provides one-click access to common tasks:
Below Quick Admin, a row of cards shows real-time metrics:
| Card | What It Shows |
|---|---|
| Open Tickets | Number of tickets in Open status, awaiting assignment or triage. |
| In Progress | Tickets currently being worked on by experts. |
| SLA at Risk | Tickets approaching or past their SLA deadline. Click to filter the ticket list. |
| Resolved Today | Tickets resolved in the current calendar day. |
| Avg Response Time | Average time from ticket creation to first expert response. |
| CSAT Score | Average customer satisfaction rating (1–5 stars). |
The dashboard includes a live AI Insights section showing recent trends detected by ServiFlow’s AI engine — volume spikes, recurring issues, and SLA risks. See AI Insights Dashboard for details.
The Customer Satisfaction panel shows your average rating, star distribution, and recent feedback comments. This helps you spot service quality issues at a glance.
When you log in as an expert, the dashboard focuses on your personal workload. Three tabs control the left panel: Focus, Requests, and My Tickets.
A summary of tickets assigned to you, grouped by status (Open, In Progress, Paused). Click any ticket to open the detail view. Use the filter dropdown (All Mine, Claimed, Due Today, SLA Risk) to narrow the list.
A prioritised view that merges your tickets and pool tickets into a single, tiered list. Tickets are ranked by urgency tiers (T1–T5) so you always know what to work on next. See Focus Queue for details.
Unassigned tickets available in the pool, ranked by AI priority score. Claim tickets to reserve them, then accept ownership. See Expert Pool.
The right-hand sidebar shows AI Insights, Recent Assets, and Live Chat by default. When you activate Ticket Peek, these are temporarily replaced by a detailed preview of the selected ticket.
A feed of recent activity on your tickets — new comments, status changes, SLA warnings, and customer replies.
Customers see a modern, gradient-styled dashboard focused on their support requests. The interface uses friendly terminology ("Requests" instead of "Tickets") and a clean two-column layout.
A list of all requests you have raised, with current status, priority, and last update time. Click any request to view details, add comments, or accept a resolution. Filters let you narrow by status and priority.
Click the New Request button to submit a support request. Fill in the title, description, priority, and category. You can also raise requests by email or via the AI chatbot.
The Trending section shows a category breakdown of recent tickets, helping you see which types of issues are most common across your company.
If you have CMDB items linked to your account, the My Equipment card shows them. Click to open the asset list view.
Company Admins can toggle a Show Monitoring Events switch to include or exclude system/monitoring tickets from the request list. This helps distinguish between automated alerts and human-raised requests.
If you are a Company Admin, you gain additional capabilities:
There are three ways to create tickets in ServiFlow:
Click New Ticket from the dashboard or ticket list. Fill in:
| Field | Required | Description |
|---|---|---|
| Title | Yes | A short summary of the issue. |
| Description | Yes | Full details of the problem or request. |
| Priority | No | Low, Medium, High, or Critical. Defaults to Medium. |
| Category | No | e.g. Infrastructure, Database, Network. Used for SLA assignment and AI classification. |
| Customer | Admin only | Which customer is raising this request. Auto-filled for customer users. |
When email integration is configured, any email sent to your support address automatically creates a ticket. The sender is matched to a customer by their email domain. See Email to Ticket.
Customers can type raise ticket: [description] in the chat widget to create a ticket without leaving the current page. See AI Chatbot.
When a ticket is created, ServiFlow automatically:
created activity entryThe ticket list is your main workspace for managing tickets.
Use the filter bar at the top to narrow the list:
The search box performs a text search across ticket titles and descriptions. Results update as you type.
Click any column header to sort the list. Click again to reverse the sort order. Common sort columns include created date, priority, status, and SLA deadline.
Select multiple tickets using the checkboxes, then choose a bulk action:
| Action | Description |
|---|---|
| Close Selected | Mark all selected tickets as Closed. |
| Resolve Selected | Resolve all selected tickets with a shared resolution note. |
| Assign Selected | Assign all selected tickets to a chosen expert. |
Click the Export button to download the current filtered ticket list as a CSV file, including all visible columns.
Click any ticket to open its full detail view.
The top section shows the ticket ID, title, current status badge, priority badge, category, requester name, assigned expert, and creation date.
If an SLA is applied, two live countdown timers appear:
Timers are colour-coded:
| Colour | Meaning |
|---|---|
| Green | On track — plenty of time remaining |
| Amber | Near breach — approaching the deadline (85% of time elapsed) |
| Red | Breached — the deadline has passed |
Deadlines are shown as absolute timestamps below each timer (e.g. Response due: 2026-02-14 09:30).
A chronological log of everything that has happened on the ticket:
On the right side of the ticket detail, the AI panel shows:
Each suggestion has Accept and Dismiss buttons. See AI Assist.
Every ticket moves through a defined set of statuses:
Open → In Progress → Paused → Resolved → Closed
| Status | Description | SLA Effect |
|---|---|---|
| Open | New ticket awaiting assignment or triage. | Response and resolve timers are running. |
| In Progress | An expert is actively working on the ticket. | Moving from Open to In Progress records first_responded_at and stops the response timer. |
| Paused | Waiting for customer response or external input. | SLA timers are paused. Time spent waiting is not counted. |
| Resolved | The expert has applied a fix. Awaiting customer confirmation. | Resolve timer stops. |
| Closed | Completed — no further action needed. | SLA timers stopped. CSAT feedback may be requested. |
Certain status transitions require a note:
The actions available depend on your role and the ticket's current state.
| Action | Description |
|---|---|
| Self-Assign | Claim an unassigned ticket. Sets you as the assignee and moves the ticket to In Progress. |
| Resolve | Mark the ticket as resolved. Opens the completion modal for a resolution note. |
| Release Claim | Release a claimed pool ticket back to the pool so another expert can pick it up. |
| Action | Description |
|---|---|
| Reassign | Transfer the ticket to a different expert. Opens the reassign modal. |
| Escalate | Flag the ticket as escalated. Sets the escalated_at timestamp. |
| Take Over | Take ownership of a ticket from another expert. |
| Mark as System | Flag the ticket as a monitoring/system alert (e.g. Nagios, Zabbix). Marked with a satellite dish icon. |
| Action | Description |
|---|---|
| Add Comment | Post a comment to the ticket activity feed. |
| Accept Resolution | Confirm the fix is satisfactory. Moves the ticket to Closed. |
| Decline Resolution | Reject the fix with a reason. Reopens the ticket to In Progress. |
The Expert Pool is a shared queue of unassigned tickets, ranked by AI priority scoring, that experts can claim.
ServiFlow's AI engine scores each pool ticket based on:
| Status | Meaning |
|---|---|
| Available | Ticket is in the pool, unclaimed, and ready for any expert. |
| Claimed | An expert has claimed the ticket but has not yet accepted full ownership. |
| Accepted | The expert has accepted ownership. The ticket moves to their personal queue. |
The Focus Queue is a unified, prioritised list that merges your assigned tickets and pool tickets into a single view. Instead of jumping between tabs, you see everything ranked by urgency.
Every ticket in the Focus Queue is assigned one of five tiers. Tiers are evaluated in order — the first matching rule wins.
| Tier | Criteria | Colour | Meaning |
|---|---|---|---|
| T1 | SLA resolve breached | Red | Immediate attention — SLA has been missed. |
| T2 | SLA resolve near breach | Amber | At risk — breach is imminent. |
| T3 | Assigned to you (not breached) | Blue | Your tickets that are on track. |
| T4 | Pool ticket, High/Critical priority | Purple | Important pool tickets worth claiming. |
| T5 | Pool ticket, Normal/Low priority | Grey | Routine pool tickets. |
Within the same tier, tickets are sorted by most recently updated first.
Each row shows:
Hover over any row to reveal quick-action buttons: Resolve, Reassign, and Comment. Click a row to open the full ticket detail.
Ticket Peek gives you an instant preview of a ticket without leaving the queue. It replaces the right-hand sidebar (AI Insights, Assets, Chat) with a detailed panel.
The peek panel loads instantly from cached data, with no extra API call for the initial view:
After the instant render, two additional sections load asynchronously:
While peek is open, pressing j or k moves to the next/previous ticket and the peek panel updates automatically. This lets you rapidly scan through your queue.
From peek, click Open Full or press Enter to navigate to the full ticket detail view.
The expert dashboard supports keyboard-driven navigation for fast triage. Shortcuts are active on the Focus and My Tickets tabs when no input field is focused.
| Key | Action |
|---|---|
| j | Move highlight down to the next ticket |
| k | Move highlight up to the previous ticket |
| Enter | Open the highlighted ticket in full detail view |
| Key | Action |
|---|---|
| p | Toggle the peek panel open/closed for the highlighted ticket |
| Key | Action |
|---|---|
| r | Resolve the highlighted ticket |
| a | Reassign the highlighted ticket |
| c | Add a comment to the highlighted ticket |
When a new ticket is created, ServiFlow's AI engine automatically analyses the title and description to classify it.
| Field | Description |
|---|---|
| Work Type | Incident, Service Request, Question, Feedback, Operational Action, or Unknown. |
| Category | e.g. Infrastructure, Database, Storage, Network, Performance. |
| Sentiment | Positive, Neutral, Negative, or Mixed. |
| Root Cause | System, Hardware, Software, Network, Database, or Resource. |
| Impact Level | Low, Medium, High, or Critical. |
| Confidence Score | 0–100% indicating how certain the AI is about its classification. |
| Key Phrases | Technical terms and important phrases extracted from the description. |
| Estimated Resolution Time | AI-predicted time to resolve based on similar past tickets. |
Admins and experts can override any AI classification by editing the ticket's category, priority, or work type fields. The override is logged in the activity feed.
The AI Assist panel appears on the right side of the ticket detail view, providing intelligent suggestions to help experts resolve tickets faster.
| Section | What It Provides |
|---|---|
| Summary | A concise AI-generated summary of the ticket content. |
| Urgency | A recommended urgency level based on content analysis. |
| Sentiment | Detected customer sentiment with confidence indicator. |
| Draft Response | A suggested reply that the expert can edit before sending. |
| CMDB Matches | Configuration items that may be related to the issue. Accept to link them to the ticket. |
| Next Steps | An ordered list of recommended actions. |
| Warnings | Critical concerns or issues flagged by the AI. |
Each suggestion has two buttons:
You can also click Accept All or Dismiss All at the top of the panel.
The AI Insights dashboard surfaces trends and patterns detected across your tickets.
Choose the analysis window: Last 7 days, Last 30 days, or Last 90 days. The dashboard refreshes to show trends for the selected period.
| Action | Description |
|---|---|
| Refresh | Reload the latest insights from the AI engine. |
| Detect Trends | Manually trigger a fresh trend analysis. |
| Acknowledge | Mark an insight as reviewed. Records your name and timestamp. |
| Dismiss | Remove a false positive or resolved insight from the view. |
The AI chatbot is a floating widget in the bottom-right corner of the screen, available to customers for self-service support.
| Command | Description |
|---|---|
raise ticket: [description] | Create a new support ticket directly from the chat. |
status #123 | Check the current status of a specific ticket. |
my tickets | List all your open tickets. |
help | Show available commands. |
The chatbot searches the knowledge base for answers before creating a ticket. If a relevant article is found, it is shown to the customer. If not, the chatbot offers to raise a ticket.
ServiFlow can automatically generate knowledge base articles from resolved tickets.
auto_generated and saved as Draft status.The AI identifies similar existing articles and suggests merging them to avoid duplication. You can Accept a merge (combining the articles) or Dismiss the suggestion.
ServiFlow includes a built-in live chat system that lets customers communicate with experts in real time.
Admins can configure Canned Responses in Settings > Canned Responses — pre-written reply templates that experts can insert into a chat with one click. This speeds up responses for common questions.
When a new chat message arrives, a notification badge appears on the chat icon. Desktop notifications are also sent if the browser supports them.
A Service Level Agreement (SLA) defines how quickly your team should respond to and resolve tickets. ServiFlow tracks SLAs in real time with countdown timers, colour-coded warnings, and breach notifications.
| Metric | Definition | Starts | Stops |
|---|---|---|---|
| Response Time | Time until the first expert response | Ticket creation | First status change from Open (sets first_responded_at) |
| Resolution Time | Time until the ticket is resolved | Ticket creation | Ticket status moves to Resolved |
SLA timers only count time during your defined business hours. If your business hours are Mon–Fri 09:00–17:00, a ticket created at 16:00 on Friday with a 4-hour response SLA would be due at 12:00 on Monday — not 20:00 on Friday.
Go to SLA Management > Definitions to create and manage SLA definitions.
| Field | Description |
|---|---|
| Name | A descriptive label, e.g. "Critical — 1hr Response". |
| Category | Optional category label for grouping. |
| Response Time (hours) | Maximum hours allowed before first response. |
| Resolution Time (hours) | Maximum hours allowed before resolution. |
| Business Hours Profile | Which business hours profile to use for time calculations. |
| Active | Toggle the definition on or off. |
| Name | Response | Resolution | Hours Profile |
|---|---|---|---|
| Critical | 1 hour | 4 hours | 24x7 |
| High | 2 hours | 8 hours | Business Hours |
| Standard | 4 hours | 24 hours | Business Hours |
| Low | 8 hours | 48 hours | Business Hours |
Business hours profiles define when your team is available. SLA timers only count time during these periods.
| Field | Description |
|---|---|
| Name | e.g. "EMEA Business Hours", "24x7 Support" |
| Timezone | IANA timezone (e.g. Europe/London, US/Pacific, Australia/Sydney) |
| Working Days | Select which days of the week are working days (Mon=1 to Sun=7) |
| Start Time | When the working day starts (e.g. 09:00) |
| End Time | When the working day ends (e.g. 17:00) |
| 24x7 | Toggle for round-the-clock coverage. Overrides start/end times and working days. |
When a ticket is created, ServiFlow automatically assigns an SLA definition using a priority cascade. The first match wins:
Once applied, the SLA sets response_due_at and resolve_due_at timestamps, and the countdown timers begin.
Map ticket categories to SLA definitions so that tickets are automatically assigned the correct SLA based on their category.
ServiFlow sends email notifications at three thresholds for both response and resolution SLAs:
| Threshold | Trigger | Who Is Notified |
|---|---|---|
| Near Breach | ~85% of the allowed time has elapsed | Assigned expert + admins |
| Breached | 100% — the deadline has passed | Assigned expert + admins |
| Past Breach | ~120% — significantly overdue | Assigned expert + admins |
Each notification is sent only once per ticket per threshold (tracked via timestamp columns like notified_response_near_at). The SLA notifier runs on a schedule to check all active tickets.
When a ticket moves to Paused status (typically "Waiting on Customer"), the SLA timers pause. The customer's response time is not counted against your SLA targets.
The Configuration Management Database (CMDB) is your central inventory of IT assets — servers, network devices, software, databases, and more. Linking tickets to CMDB items helps you track which assets are affected and apply the correct SLAs.
Assets are organised by category. Common categories include:
| Field | Description |
|---|---|
| Asset Name | Unique identifier for the asset (e.g. PROD-WEB-01) |
| Asset Category | The type of asset (e.g. Windows Server) |
| Brand | Manufacturer (e.g. Dell, HP, Cisco) |
| Model | Product model (e.g. PowerEdge R740) |
| Customer | Which customer owns or uses this asset |
| Employee Of | The employee responsible for the asset |
| Location | Physical or logical location |
| Status | Active, Inactive, Retired, Maintenance |
| SLA Definition | Optional SLA to apply when tickets are linked to this asset |
The Asset Viewer provides a powerful grid-based view of all CMDB assets, built on DataTables for fast searching, sorting, and pagination.
The asset grid displays: ID, Asset Name, Category, Brand, Model, Customer, Location, and Status. Click any column header to sort. Use the search box to filter across all columns.
Dedicated filter dropdowns let you narrow assets by Customer, Category, Brand, and Model. Filters can be combined for precise results.
Click any asset row to open the detail panel on the right. This shows all asset fields, configuration items (CIs), linked tickets, and custom field values. Click Edit to modify asset details inline.
Click Export to CSV to download all assets (or the current filtered set) as a CSV file.
Asset Categories define the types of assets in your CMDB. Categories are managed centrally and appear as dropdown options when creating or editing assets.
Go to CMDB > Settings > Asset Categories to add, edit, or remove categories. Common categories include: Windows Server, Linux Server, Network Infrastructure, Hardware, Software, Database, VoIP, and Service.
In addition to categories, you can manage Brands (manufacturers like Dell, Cisco, Microsoft) and Models (specific products like PowerEdge R740, Catalyst 9300). These appear as dropdowns in asset forms for consistent data entry.
Each asset category can have custom fields tailored to that type of asset.
| Type | Description |
|---|---|
| Text | Free-text input |
| Number | Numeric input |
| Date | Date picker |
| Dropdown | Select from a predefined list of options |
For each custom field, you can set a label, description, default value, and whether it is required.
CMDB items can be linked in parent/child relationships to model your infrastructure topology.
The dependency tree shows a hierarchical indented view of how assets relate to each other. For example:
Data Centre (Parent)
├── Server Rack A
│ ├── PROD-WEB-01 (Windows Server)
│ └── PROD-WEB-02 (Windows Server)
└── Server Rack B
└── PROD-DB-01 (Database)
When a parent asset has an issue, the dependency tree helps you identify which child assets and services may be affected.
Every change to a CMDB item is automatically logged in the change history. This provides a full audit trail of who changed what and when.
| Event | Details Recorded |
|---|---|
| Created | Who created the asset, initial values |
| Updated | Which field changed, old value, new value, who made the change |
| Deleted | Who deleted the asset |
Each entry also records the user's IP address and timestamp.
Click Export to download all CMDB items as a CSV file.
Linking tickets to CMDB items provides context about which assets are affected and can influence SLA assignment.
If a linked CMDB item has an SLA definition assigned, that SLA can be applied to the ticket (see How SLAs Apply — step 4 in the cascade).
The Knowledge Base (KB) is a library of articles that help customers find answers without raising a ticket, and help experts resolve issues faster.
The KB dashboard shows total articles, published articles, draft articles, total views, and helpfulness ratings.
| Field | Description |
|---|---|
| Title | The article headline. |
| Content | Rich-text body of the article. |
| Summary | A brief description shown in search results. |
| Category | Organise articles by topic. |
| Tags | Keywords for search and filtering. |
| Status | Draft (not visible to customers) or Published (visible). |
| Visibility | Public (all users), Internal (staff only), or Customer (customers only). |
Each article tracks view count, helpful count, and not-helpful count. Use these metrics to identify popular articles and those that need improvement.
Customers can browse and search published articles from the Knowledge Base tab in their portal.
The AI chatbot also searches the KB automatically when customers ask questions.
When tickets are resolved, ServiFlow's AI can automatically generate draft KB articles from the issue description and resolution notes. See AI KB Generation for details.
auto_generated and status Draft.ServiFlow can monitor an email inbox and automatically create tickets from incoming messages. Two email providers are supported: Standard IMAP and Microsoft 365.
The Email Ingest settings page is organised into two provider tabs. Each tab has its own Enable toggle, Outbound toggle, Test Connection button, and Check Interval setting. The providers are independent — enabling IMAP does not affect M365 and vice versa.
| Field | Example (Gmail) | Example (Outlook) |
|---|---|---|
| Server Host | imap.gmail.com | outlook.office365.com |
| Server Port | 993 | 993 |
| Use SSL | Yes | Yes |
| Username | support@company.com | support@company.com |
| Password | App Password | App Password |
myaccount.google.com/apppasswords.You can designate specific email addresses as System Senders (e.g. nagios@company.com). Emails from these addresses create tickets under the "System" user instead of auto-creating customer accounts. ServiFlow also has built-in detection for common monitoring systems (Nagios, Zabbix, Datadog, etc.) and parses their alerts specially — extracting host, service, alert type, and state. See Alert Correlation for how recovery alerts automatically close previous alert tickets.
ServiFlow can connect to a Microsoft 365 mailbox using the Microsoft Graph API with client credentials (app-only) authentication.
Your Microsoft 365 administrator must complete the following one-time setup to allow ServiFlow to read the shared mailbox.
admin.exchange.microsoft.com).ServiFlow-Mail-Access.support@company.com) as a member.Open Exchange Online PowerShell and run:
Connect-ExchangeOnline
New-ApplicationAccessPolicy `
-AppId "<ServiFlow-App-Client-ID>" `
-PolicyScopeGroupId "ServiFlow-Mail-Access" `
-AccessRight RestrictAccess `
-Description "ServiFlow email ingest"
Replace <ServiFlow-App-Client-ID> with the Application (client) ID provided in your ServiFlow settings. The policy takes up to 30 minutes to propagate.
When a customer replies to a ticket notification email, ServiFlow matches the reply to the existing ticket using four methods (tried in order):
| # | Method | How It Works |
|---|---|---|
| 1 | Header Threading | Checks the In-Reply-To and References email headers for a matching message ID. |
| 2 | Subject Token | Looks for [Ticket #NNNN] in the subject line. |
| 3 | URL Parsing | Scans the email body for links to /ticket/view/[token]. |
| 4 | Subject + Domain Match | Falls back to matching the subject line combined with the sender's domain. |
The first match wins. If no match is found, a new ticket is created.
[Ticket #NNNN] token from the subject and don't preserve In-Reply-To headers. If threading is not working, check with the customer's email client.When a new ticket is created from an incoming email, ServiFlow sends an automatic confirmation email to the sender.
Auto-reply can be toggled on or off per tenant in Settings > Email Ingest.
Each email provider (IMAP and M365) has its own Enable Outbound Notifications toggle. When enabled, ticket notifications and system emails are sent from that provider's mailbox instead of the default system email.
When outbound is enabled on the IMAP tab, you can configure separate SMTP Server Host and SMTP Port for sending emails.
When outbound is enabled on the M365 tab, emails are sent via the Microsoft Graph API using the same mailbox configured for ingest.
The Company Email Notifications grid (at the bottom of the Email Ingest settings page) gives you a consolidated view of email preferences for all customer companies.
| Column | Description |
|---|---|
| Company | The customer company name. |
| Admin | The company admin's name. |
| Admin Receives Emails | When checked, the company admin receives ticket notifications for all company tickets. |
| Members Receive Emails | When checked, individual team members receive ticket notifications for their own tickets. |
Toggle any checkbox to update the setting immediately. Changes take effect on the next notification event.
ServiFlow sends email notifications for key ticket events. These can be enabled or disabled via Settings > System Control.
| Event | Sent To |
|---|---|
| Ticket created | Requester (customer) |
| Ticket assigned | Assigned expert |
| Status changed | Requester + assigned expert |
| Customer reply received | Assigned expert |
| Expert reply posted | Requester |
| Ticket resolved | Requester (with acceptance link) |
| SLA near breach | Assigned expert + admins |
| SLA breached | Assigned expert + admins |
| SLA past breach | Assigned expert + admins |
Go to Customers in the sidebar to manage your customer accounts.
acme.com).A random secure password is generated and can be sent to the customer. The password is hashed immediately — it cannot be retrieved later, only reset.
Companies group multiple customer users under one organisation and enable domain-based email routing.
| Field | Description |
|---|---|
| Company Name | The organisation name (e.g. "Acme Corp"). |
| Company Domain | Email domain used for automatic routing (e.g. acme.com). |
| Contact Email | Primary contact email for the company. |
| Phone | Company phone number. |
| Address | Company address. |
| SLA Level | Company-wide SLA level (Basic, Premium, Enterprise). |
| Admin Receives Emails | Whether the company admin gets ticket notifications for all company tickets. |
| Members Receive Emails | Whether individual members get ticket notifications for their own tickets. |
| Notes | Internal notes (not visible to customers). |
When an email arrives from john@acme.com, ServiFlow extracts the domain acme.com, looks it up in the companies/customers table, and creates the ticket under that customer. If no user exists for that email, a new customer account is created automatically.
You can assign an SLA level to a company. All tickets from users in that company will inherit this SLA (unless overridden at the user level). See How SLAs Apply.
The customer portal is a modern, gradient-styled interface that customers see when they log in. It uses friendly terminology ("Requests" instead of "Tickets") and a streamlined navigation with SVG icons.
The ticket detail view features a gradient header showing key information (status, priority, SLA), an improved activity timeline with clear visual separation, and quick-action buttons for common operations.
A customer promoted to Company Admin gains additional capabilities:
| State | Description |
|---|---|
| Pending | Invitation sent, not yet accepted. |
| Active | Expert has accepted and can log in. |
| Deactivated | Admin has deactivated the account. Expert cannot log in. |
The expert list shows each expert's open ticket count, last login time, and account creation date.
When you deactivate an expert, their account is soft-deleted. Open tickets assigned to them should be reassigned first. Deactivated experts appear in a separate "Deleted Experts" list and can be reactivated if needed.
Staff members can self-register as experts by sending an email with the subject Register_Expert to your support inbox.
apoyar.eu).Register_Expert to the support address.Experts have access to the following features:
Automated Actions are AI-powered rules that automatically process tickets matching specific criteria. They replace the older keyword-based ticket processing rules with more flexible, intelligent matching.
Actions can be restricted to tickets from specific sources: email, web, chatbot, or all. This lets you create actions that only apply to, say, tickets created from inbound email.
| Field | Description |
|---|---|
| Rule Name | A descriptive label (e.g. "Auto-assign Infrastructure Alerts"). |
| Search In | Where to search: title, body, or both. |
| Search Text | The text pattern to match. |
| Case Sensitive | Whether the match should be case-sensitive. |
| Source Filter | Restrict to a specific ticket source (email, web, chatbot, or all). |
| Action Type | The action to perform on matching tickets. |
| Instruction Text | AI instruction or additional context for the action. |
| Enabled | Toggle the action on or off without deleting it. |
| Action | Description | Parameters |
|---|---|---|
| Delete | Delete matching tickets (e.g. spam) | None |
| Assign to Expert | Auto-assign to a specific expert | Expert selection |
| Create for Customer | Reassign to a different customer | Customer selection |
| Set Priority | Set ticket priority | Priority (Low / Medium / High / Critical) |
| Set Status | Set ticket status | Status (Open / In Progress / Paused / Resolved / Closed) |
| Add Tag | Add tags to the ticket | Tag values |
| Close Ticket | Close the ticket with an activity log entry | Optional closure note |
Before enabling an action, use the Test button to preview which tickets would match without actually executing the action. This shows a list of matching tickets so you can verify the search pattern is correct.
Click Run on an action to execute it once against all current tickets. This is useful for applying a new action to existing tickets.
For actions that match many tickets, ServiFlow processes them in batches. You can configure batch size and interval in the support settings.
Each action maintains a history of its executions, including timestamps, number of matches, and results (success or failure).
| Goal | Search Text | Source | Action |
|---|---|---|---|
| Auto-assign server alerts | Infrastructure Monitoring | Assign to Expert | |
| Escalate urgent requests | URGENT | All | Set Priority (Critical) |
| Tag password reset tickets | password reset | All | Add Tag ("password-reset") |
| Auto-close marketing emails | unsubscribe | Close Ticket |
ServiFlow automatically correlates monitoring alerts by host and service, so that when a recovery notification arrives, the original alert ticket is closed automatically. This eliminates the need to manually close resolved alerts and reduces monitoring ticket noise by 80–90%.
When ServiFlow processes an email from a monitoring system (Nagios, Zabbix, etc.), it extracts three key fields from the email body:
| Field | Pattern | Example |
|---|---|---|
| Host | Host: <value> | HRMS Apoyar |
| Service | Service: <value> | TTFB |
| State | State: <value> | OK, WARNING, CRITICAL |
These fields are combined into a correlation key (tenant|host|service) and stored in the ticket's metadata.
A typical monitoring incident follows this timeline:
| Time | Event | Result |
|---|---|---|
| 03:12 | WARNING alert for Server1/CPU Load | Ticket #884 created (Open) |
| 03:19 | RECOVERY alert for Server1/CPU Load | Ticket #884 closed automatically by correlation |
| 03:19 | (same RECOVERY email) | OK ticket #885 created and closed by Automated Action rule |
The result is a clean audit trail: one alert ticket per incident, closed when the service recovers.
OK, source filter System/Monitoring Only, and action Close Ticket.Host:, Service:, and State: lines in its notification emails (Nagios, Icinga, Zabbix, etc.).The Analytics dashboard provides visual insights into your service desk performance.
Choose from Last 7 days, Last 30 days, or Last 90 days to adjust all charts and metrics.
| Metric | Description |
|---|---|
| Total Tickets | All tickets created in the selected period. |
| Open Tickets | Currently open tickets. |
| In Progress | Tickets being actively worked on. |
| Resolved Today | Tickets resolved in the current day. |
| SLA at Risk | Tickets approaching or past their SLA deadline. |
| Avg Response Time | Average hours from creation to first response. |
| Metric | Description |
|---|---|
| Total with SLA | Tickets that have an SLA definition applied. |
| Met SLA | Tickets resolved within the SLA deadline. |
| Missed SLA | Tickets resolved after the deadline. |
| Breached | Tickets currently past their deadline. |
| Compliance % | Percentage of tickets meeting SLA targets. |
Click Export to download the analytics data as a CSV file for further analysis in Excel or other tools.
Customers see a simplified analytics view showing only their own tickets: total created, currently open, and average response time.
Monthly Reports provide a formatted summary of ticket activity for a selected company over a chosen month.
Admins can configure automatic monthly report delivery. Reports are generated and emailed on the first day of each month for the previous month's data.
Company Admin customers can also access Monthly Reports for their own company, giving them self-service visibility into their support metrics.
Connect ServiFlow to Microsoft Teams to receive ticket notifications and manage tickets directly from your Teams channels.
Connect ServiFlow to Slack to post ticket updates and receive notifications in your Slack workspace.
| Event | Notification |
|---|---|
| Ticket created | New ticket posted to the channel. |
| Status changed | Update posted as a thread reply. |
| SLA at risk / breached | Warning posted with ticket link. |
| Customer reply | Reply notification posted. |
| Assigned to you | Direct message or channel mention. |
Go to Settings > Tenant Settings to configure your company profile.
| Field | Description |
|---|---|
| Company Name | Your organisation name, displayed in emails and the portal. |
| Logo | Upload your company logo (displayed in the header and emails). |
| Support Email | The primary support email address shown to customers. |
| Phone Number | Support phone number. |
| Website | Your company website URL. |
| Support Hours | Description of your support availability. |
Go to Settings > Email Ingest to configure inbound email processing. The settings are organised into two provider tabs (IMAP and M365), each with independent controls.
Each provider tab includes its own:
Server Type (IMAP/POP3), Host, Port, SSL, Username, Password, and optional SMTP fields for outbound.
Mailbox Email Address, connection status indicator, and one-time setup instructions for your M365 admin.
The Email Ingest page also includes System Senders (addresses treated as monitoring sources) and Company Email Notifications (per-company notification toggles).
See Email to Ticket and Microsoft 365 Email for full setup guides.
Sensitive configuration settings are grouped under System Admin Tools in a collapsible sidebar section. Accessing these tools requires password re-authentication (elevation) to prevent accidental changes.
When you click System Admin Tools, a password prompt appears. Enter your admin password to gain elevated access for 30 minutes. An Elevated badge appears in the sidebar while active.
System control provides toggles to enable or disable major features.
| Toggle | Description |
|---|---|
| Process Emails | Enable or disable inbound email ticket creation. |
| Send Notifications | Master kill switch for all outbound email notifications. |
| Feature Flags | Enable or disable experimental features. |
| Batch Controls | Configure batch size and interval limits for rule processing. |
Housekeeping manages data retention by automatically removing old, closed tickets and their activity logs based on configurable retention periods.
| Plan | Default Retention |
|---|---|
| Starter | 90 days |
| Professional | 180 days |
| MSP | 365 days |
You can override the default retention period for your tenant in the housekeeping settings.
The audit log records all significant admin actions for accountability and compliance.
Login, logout, create, update, delete, assign, reassign, resolve, close, and configuration changes are all recorded.
| Column | Description |
|---|---|
| Username | Who performed the action. |
| Action | What action was taken (e.g. create, update, delete). |
| Entity Type | What was affected (e.g. ticket, customer, expert, SLA). |
| Entity ID | The ID of the affected record. |
| Details | Additional context (e.g. "Status changed from Open to In Progress"). |
| IP Address | The user's IP address. |
| Timestamp | When the action occurred. |
Filter the audit log by user, action type, or date range. Click Export to download the log as a CSV file.
Raw Variables is a comprehensive configuration viewer that surfaces all system settings in one place. It aggregates data from 12 sections covering tenant settings, email configuration, SLA definitions, automation rules, customer company config, CMDB settings, user notification preferences, and more. Found under Settings → Raw Variables (labelled "Developer Mode").
| Section | Source | Editable | Description |
|---|---|---|---|
| Tenant Settings | tenant_settings | Yes | Custom key-value config, feature flags, thresholds |
| IMAP Ingest | email_ingest_settings | Yes | IMAP server, credentials, polling interval |
| Microsoft 365 | email_ingest_settings | Partial | Graph API / OAuth2 settings, tokens |
| Outbound / SMTP | email_ingest_settings | Yes | SMTP relay host, port, outbound toggle |
| Company Profile | company_profile | Yes | Company name, phone, email, domain |
| Feature Flags | tenant_features | No | Enabled/disabled features from subscription plan or overrides |
| SLA & Business Hours | sla_definitions, business_hours_profiles | No | SLA response/resolve targets, schedules |
| Automation & Chat | ticket_processing_rules, chat_canned_responses | No | Ticket rules (match/action), canned chat messages |
| Customer Companies | customer_companies | No | Per-company SLA level, notification settings |
| CMDB Configuration | asset_categories, cmdb_custom_field_definitions | No | Asset categories, custom field counts |
| Users & Notifications | users | No | Admin/expert email notification preferences |
| Environment | Server process env | No | NODE_ENV, BASE_URL, PORT |
Custom key-value pairs stored in the tenant_settings table. Common keys include:
send_emails_experts / send_emails_customers — global email notification togglesprocess_sla — enable/disable SLA breach checkingmonthly_report_enabled / monthly_report_recipients — automated reportingcustomer_billing_enabled / enhanced_sla_billing_mode — billing configbatch_delay_seconds / batch_size — email batch processingUse + Add Variable to create new keys, Edit to change values, and Delete to remove custom keys.
Configuration for IMAP email-to-ticket polling:
| Key | Description |
|---|---|
enabled | Enable/disable IMAP polling |
server_type | Protocol: imap or graph |
auth_method | Authentication: basic or oauth2 |
server_host / server_port / use_ssl | IMAP server connection details |
username / password | Mailbox credentials (password masked) |
check_interval_minutes | Polling frequency |
last_checked_at | Last poll timestamp (read-only) |
imap_locked_by / imap_lock_expires | Worker lock status (read-only) |
Graph API / OAuth2 configuration for M365 mailbox integration:
| Key | Description |
|---|---|
m365_enabled | Enable Microsoft 365 ingestion |
oauth2_email | M365 mailbox email address |
oauth2_refresh_token | OAuth2 refresh token (masked) |
oauth2_access_token | Current access token (read-only, masked) |
oauth2_token_expiry | Token expiry timestamp (read-only) |
graph_delta_link | Graph API delta link (read-only) |
m365_use_for_outbound | Use M365 for sending replies |
| Key | Description |
|---|---|
use_for_outbound | Enable SMTP relay for outbound emails |
smtp_host / smtp_port | SMTP server address and port |
| Key | Description |
|---|---|
company.name | Company display name |
company.contact_phone | Support phone number |
company.mail_from_email | From address for notifications |
company.url_domain | Company website/portal domain |
The following sections pull live data from their respective tables. They are read-only in Raw Variables — use the dedicated management UIs to modify them.
Shows all features from the tenant_features table, including those granted by the subscription plan, manual overrides, and trials. Each flag shows its enabled/disabled state and source.
Lists every SLA definition with its response and resolve targets (in minutes), near-breach percentage threshold, and active status. Also shows business hours profiles with their schedules and timezones.
Shows all ticket processing rules with their enabled status, action type, match criteria, and trigger count. Also lists chat canned responses with their action type and active status.
Per-company configuration: SLA level (basic/premium/enterprise), assigned SLA definition, active status, and notification preferences (admin_emails, member_emails).
Lists all asset categories (active/inactive) and the count of custom field definitions per category.
Shows email notification preferences for every admin and expert user: email_updates (receive email updates), notifications_enabled (email notifications on), and active status.
Read-only server environment values: NODE_ENV, BASE_URL, DEFAULT_TENANT, PORT.
The search box at the top filters across all 12 sections, matching against both key names and values.
tenant_settings as a JSON file for backup or migration.email_ingest., company.) are handled automatically. Masked passwords are skipped.All Raw Variables actions are logged: opening the view, creating/updating/deleting variables (old and new values recorded), and exporting or importing. Password and token values are redacted in audit logs.
ServiFlow offers three plans to suit organisations of different sizes.
| Feature | Starter | Professional | MSP |
|---|---|---|---|
| Users | Up to 5 | Up to 25 | Unlimited |
| Tickets | Unlimited | Unlimited | Unlimited |
| Data Retention | 90 days | 180 days | 365 days |
| AI Features | Limited | Full | Full |
| Integrations | — | Teams + Slack | Teams + Slack |
| White-label | — | — | Available |
| Priority Support | — | — | Included |
New accounts start with a 30-day free trial. During the trial, you have access to all features. Your trial end date is shown in Settings > Billing.
You can downgrade to a lower plan at any time. If your current usage exceeds the lower plan's limits (e.g. more users than allowed), you will need to deactivate users before the downgrade takes effect.
Click Cancel Subscription in the billing settings. Your account remains active until the end of the current billing period.
View past invoices and payment history in the billing section.
The Usage dashboard shows how much of your plan's allowance you are using.
| Metric | Description | Starter Limit | Professional Limit | MSP Limit |
|---|---|---|---|---|
| Users | Total active user accounts | 5 | 25 | Unlimited |
| Tickets | Tickets created this month | Unlimited | Unlimited | Unlimited |
| Storage | File storage used | 10 GB | 100 GB | Unlimited |
Each metric is displayed with a colour-coded progress bar:
When you hit a plan limit:
ServiFlow warns you when you reach 80% of a limit: