← Back to Module Index
Module 04 · Execution

Execution

Execution is where day-to-day regulatory work happens — standalone assignments, return filings, client queries, eSign requests, and document collection. This module covers each sub-area step by step.

Sub-modulesService Desk · Return Tracker · Client Queries · eSign · Doc Requests
Who uses thisConsultants, compliance managers, back-office staff

Service Desk

Service Desk handles standalone service work that is not part of a project — e.g., monthly GST filing, annual MCA forms, ad hoc advisory.

Creating a Service Assignment

1

Go to Execution → Service Desk → + New Assignment

Fill in: Client, Service Type, Team (not individual — a team owns it first), SLA date, and description.

2

Team Manager routes to consultant

The team manager sees unassigned items in their queue and allocates to a specific consultant. The consultant is notified in My Workspace.

3

Consultant logs time

As work progresses, the consultant logs hours via My Workspace → My Effort. Billable flag must be set correctly.

4

Submit for approval

When work is done, the consultant marks the assignment complete and submits effort for manager approval.

5

Manager approves → billing triggered

Approved effort can be included in the monthly statement or directly invoiced if the assignment is billable.

Tip — Team ownership firstNever assign directly to an individual at creation. Always assign to the team. The team manager then routes it. This preserves accountability when people are on leave.

Return Tracker

Tracks statutory return filing deadlines — SEBI quarterly submissions, RBI monthly returns, IRDAI annual filings — across all clients in one view.

ColumnMeaning
Return NameOfficial name of the regulatory return (e.g., NBS-1, ALM Returns)
ClientWhich client entity the return is for
FrequencyMonthly / Quarterly / Annual
Due DateNext filing deadline. Pre-alert sent 7 days before
StatusPending / Filed / Overdue. Click Pending to open the filing workflow
CriticalOverdue returns are flagged in Mission Control and escalated to the account manager automatically. Do not let returns stay in Overdue without updating the status.

Client Queries

Client Queries is the structured inbox for queries raised by client portal users. Every query creates a ticket with an SLA timer. Do not manage these via email — use this module.

1

Open Execution → Client Queries

Lists all open tickets sorted by SLA — most urgent at the top.

2

Click a query to open it

See the client's full question, any attachments, and conversation history.

3

Reply within ZippCRM

Type your response and click Send. The client is notified via email and can see the reply in their portal.

4

Mark Resolved when done

Sets the query to Closed and stops the SLA timer. The client receives a closure confirmation.

NoteSLA is calculated from when the query was received. Default SLA is 48 hours for standard queries and 4 hours for marked-urgent queries. These can be changed in Admin → Settings.

eSign Requests

Send documents for digital signature directly from ZippCRM. Signed documents are stored in the client's document vault automatically.

1

Go to Execution → eSign → + New Request

Select the client, upload the document, and add signatories (client contact email + any internal signers).

2

Set signing order if required

Sequential: Signer 1 must sign before Signer 2 is notified. Parallel: All signers notified simultaneously.

3

Click Send for Signature

Signatories receive an email with a secure link. No ZippCRM account required for the client to sign.

4

Monitor signature status

Status column shows: Sent → Partially Signed → Fully Signed. You are notified when all parties have signed.

5

Download or view in vault

Fully signed documents are automatically filed in the client's document vault and timestamped.

Document Requests

Use Doc Requests to formally ask a client to upload a specific document. Avoids informal email chains and keeps evidence in the system.

1

Go to Execution → Doc Requests → + New Request

Select client, project (optional), document name, due date, and instructions. Keep instructions clear — the client sees exactly what you type.

2

Click Send Request

Client is notified via email and in their portal. A pending item appears in their Documents section.

3

Client uploads the document

Upload is visible immediately in Ops Center → Uploads for your review.

4

Review and Accept / Reject

If accepted, the document is filed. If rejected, enter a reason — the client is notified and can re-upload.

Good PracticeAlways use Doc Requests instead of emailing clients asking for files. It creates an audit trail, tracks who uploaded what and when, and gives the client a clear to-do item in their portal.