EbixMeridian

Workflow and documents on the account record.

Tasks, reminders, follow-ups, and routing keep the service work moving in EbixASP, while document management with e-signatures and version control keeps the paperwork on the account it belongs to.

What the workflow module covers

The daily mechanics of servicing a book: who does what next, what was said, and where the paperwork is.

Tasks & Routing

Work is assigned as tasks and routed to the desk that owns the next step, attached to the account it concerns rather than passed around by email.

Reminders & Follow-Ups

Dated reminders and follow-ups keep open items in front of the service team until they are closed, on the account where the work lives.

Document Management

Documents file against the account record, so the policies, forms, and correspondence of a client sit with the client, findable by whoever needs them.

E-Signatures

Signatures are collected electronically, and the executed document returns to the account file instead of waiting in someone's inbox for scanning.

Version Control

Each revision of a document is kept, so the current version and the history behind it are both available when a question comes up later.

Communication Log

Calls, emails, and correspondence record on the account, so the file reads as a complete history to anyone who opens it.

Activity visible across branches

Tasks, follow-ups, and account activity are visible across branches, so a client who calls the Savannah office about work started in Atlanta reaches someone who can see the file. The question is answered from the record, not from a callback after the right person is found.

Because tasks are routed rather than forwarded, ownership of an item is always on the item itself, and open work is counted, not remembered.

Open tasks · all branches4 of 31

Renewal review · Bayfront Marine Supply

M. Chen · Savannah

Today

Certificate request · Hartwell Logistics

A. Reyes · Atlanta

Today

Endorsement follow-up · Pinewood Dental Group

D. Okafor · Macon

Aug 27

Signed application · Cordova Family

M. Chen · Savannah

Done

A service request through the system

From the client's call to the closed item, each step lands on the account record.

01

Log the request

The client request is recorded on the account, entering the system as an item of work rather than an email in one inbox.

02

Route the task

The task routes to the desk that owns the next step, with the account record and its documents already attached.

03

Work the item

Reminders and follow-ups keep the item open until it is done; documents produced along the way file against the account.

04

Close on the record

The outcome, the correspondence, and any executed documents stay on the account, where the next person will look for them.

Service records for the whole office

Workflow and document management keep the state of the work on the account file, where anyone covering the desk can see it.

Routing to the owning desk

Tasks carry their account and documents to whoever holds the next step.

Reminders until closure

Open items stay dated and visible until they are closed.

Executed documents on file

E-signed documents return to the account record as part of the file.

Version history kept

Prior revisions of a document remain available beside the current one.

Put the work
on the record

See tasks, routing, and document management run against your own service workflows in a working demo.