Consultant sign in
Enter the e-mail address you registered as a consultant. We e-mail you an OTP.
This e-mail is not registered as a consultant yet.
Register as a consultantYou get your Consultant Code by e-mailSign in with the e-mail and password your consultant sent you.
Your database is not connected yet
Your own database is being prepared. Customers can be added here as soon as it is ready. Please contact support.
Opening...
Overview
Leave & termination
OpenDashboard
Quick actions
Add a customer
Only these details are needed. The address (if you did not give it), GST, bank details and the logo can be filled by your customer in his own Settings (the colours are the default ones and can be changed there). The E-mail address and the URL name must not be used by any other customer (yours or another consultant's).
Add an existing seller as your customer
For a seller who is already registered (for example earlier, through a Consultant Code). Enter his registered e-mail. A confirmation code goes to his e-mail: ask him for it and enter it here. He needs no new registration and keeps his data.
Add many customers from Excel
- Download the empty Excel template and fill one customer per row: Business name, Tag line (not compulsory), URL name, Mobile number, Email address. Up to 100 customers at a time. A .csv file also works. A row whose e-mail ID or URL name is already used is not added and the reason is shown next to it.
- Choose the file and press Check file to see what will happen. Then press Import.
| Row | Business | Result |
|---|
DSC expiry mail
When a DSC is about to expire, an e-mail goes to the customer it belongs to. Tick Send mail for the DSC (nothing is sent until you tick it) and choose how many days before expiry the mail goes: 30 days is already set; press Add to add more days, for example 15 and 7 (one mail for each). The customer is found by the e-mail of the certificate, by the director / partner of the same name or by the business name; if it shows none or a wrong one, choose the customer yourself. An expired DSC gets no mail.
No DSC yet. Upload the certificate files in DSC details first.
| Holder name | Valid till | Days left | Customer (the mail goes to his e-mail) | Send mail | Days before expiry | Last mail |
|---|
Directors / signatory (MCA, company)
Choose the customer, then the master-data PDF of the company saved from the MCA site. The directors still on the board are listed (a director who has ceased is left out; the signatory column is not taken). Write the e-mail and mobile of each director in the list. The CIN is saved against the customer in Registration numbers.
Nothing saved yet.
| Customer | CIN | DIN / PAN | Name | Designation | Category | Date of appointment | Mobile |
|---|
Designated partners (LLP)
Choose the customer, then the master-data PDF of the LLP saved from the MCA site. The partners still in the LLP are listed (one who has ceased is left out). Write the e-mail and mobile of each partner in the list. The LLPIN is saved against the customer in Registration numbers.
Nothing saved yet.
| Customer | LLPIN | DIN / PAN | Name | Designation | Category | Date of appointment | Mobile |
|---|
Registration numbers of your customers
- Add at least one customer first.
It has the Email ID of all your customers so far (new customers appear in it the next time you download) and 64 columns: PAN, GSTIN, CIN, LLPIN, TAN, DIN, PF, ESIC, MSME and more. - Fill the numbers, keep the Email ID column as it is, then choose the file, press Check file and Save numbers. They are saved in your database against the customer's e-mail ID.
| Row | E-mail ID | Result |
|---|
Numbers saved for your customers
No registration number is saved yet. They are filled when you add a customer from a GST / MCA file, or from the Excel above. Only the columns that have a number are shown.
Send a file to a customer
Your file storage (Cloudinary) is not connected yet. Please contact support.
| Date | Customer | Title |
|---|
New document approval
Ask the admin to accept a new kind of document (for example COI). This is needed only once for each kind. Upload one sample PDF, choose which registration number identifies the customer in that document (Map ID) and write that number as it appears in the sample. The admin may correct the name, fixes the two fields of this document and shows where the number and the two fields are written. Once it says Approved, every later document of this kind goes straight to your list below - without the admin.
| Date | Document | Map ID | Status |
|---|
Upload documents (approved kinds)
No kind of document is approved yet. Ask for one in Document approval.
Your documents
No document uploaded yet.
| Party name | Name | Map ID | Period / Details | Year | Document |
|---|
Failed documents
A PDF whose kind is not approved comes here. Choose which registration number (Map ID) identifies the customer and write that number: the party name appears by itself. Fill Period / Details and Year, give the document a name, and press Save: it moves to "Your documents".
No failed document.
| Party name | Name | Map ID | Period / Details | Year | Document |
|---|
DSC details
Upload the certificate file of a Digital Signature Certificate (.cer, .crt, .pem, .der; a .pfx / .p12 file also works: its password is asked when you choose such a file, and it is never saved). All the details written inside the certificate are read and listed here. Only the public certificate is read; the private key is never kept.
Password: write the password of each DSC in the Password column of the list (it is kept encrypted).
Token number: write it at the start of the file name, then a dash, for example 1-Hardik Gandhi.cer (token 1). If a file has no number, it is still saved: type its token number in the Token no. column afterwards (the box can be edited any time).
No DSC yet. Upload a certificate file above.
| Holder name | Token no. | Class | Valid from | Valid till | Days left | Password |
|---|
Service Master
No service yet. Press "Add a service".
| Service name | Frequency | Date of task creation | Due date | Map ID | Reminders | Documents list |
|---|
Inward entry
Record what a customer has sent to the office. Choose the customer and how it came. If it belongs to a task, pick the task and it goes into that task's history; otherwise it is kept in Pending Inward.
At least one of these three is compulsory: files, upload path or remarks.
Pending Inward
Inward entries saved without a task. Use "Add to task" when the customer's task exists: the entry then goes into that task's history and leaves this list.
Nothing is pending.
| Date | Customer | Came by | Files | Upload path | Remarks | Entered by |
|---|
New request
This service is already added for you. A customer raises it from the New request tab of his dashboard and it comes to you as a task. Its details are fixed; you only choose the employee who gets the requests and the customers who can use it.
| Service name | New request |
|---|---|
| Sub-task | New request |
| Frequency | One time |
| Task creation date | The day the customer raises the request |
| Due date | 3 days after that |
Customers who can raise it
No customer yet.
Applicable customers
Every customer who has the service's Map ID number is listed as Applicable. Untick a customer to remove him from that service (or tick again to bring him back), then press Save changes.
No customer matches yet. Add a service in Service Master and save the registration numbers of your customers.
| Service name | Customer name | Map ID | Status |
|---|
Create task
Bulk message
Choose in any order. Each box shows only what fits the boxes before it. You can tick many in every box.
| Task no. | Service name | Customer name | Sub task name | Pending status |
|---|
Task list
No task yet. Create one in Create task.No sub-task is allotted to you yet. When the admin allots one, it appears here; open it to read the help, write notes and attach files.
| Task no. | Service name | Customer name | Sub task name | Next sub task | Pending status | Days (Sub task / Service / Total) | Allotted to | Files |
|---|
Tasks referred to me by other employees
These tasks were referred to you by another employee, because you are the head employee of the service. Open one to work on it (notes, files, Complete). Only the employee who has the sub-task can change its pending status.
No task is referred to you.
| Task no. | Service name | Customer name | Sub task name | Pending status | Referred by | Referred on | Days (Sub task / Service / Total) |
|---|
Completed tasks
No completed task yet.
| Task no. | Service name | Customer name | Status | Done in |
|---|
AI answers
AI helper key
By default the free helper of the administrator answers. If you add your own key (Google AI Studio or OpenRouter), all your employees use it and the free helper stops for you.
Answers about a customer's own case (his return, invoices, outstanding...). When the employee sends a reply after pressing "Reply", the sent text is saved here with its keywords. The next time the same customer asks the same thing, the saved answer is shown at once and the AI is not used. Common questions (rates, sections, procedures) are saved by the system in the background and are not listed.
| Customer | Keywords | Question | Answer sent | Used | Saved |
|---|
Sub-Task table
The Sub-Task name is shown to your customer in his dashboard. Sub-Task name and Employee are compulsory. Group, description, help files and help URL (all optional) are shown to your employees (they can see them but cannot change them).
Groups
No group yet. Write a group name in the Group box above and press Add.
| # | Group name | Sub-Tasks |
|---|
Sub-Tasks
No sub-task yet.
| # | Sub-Task | Group | Employee | Days required | Description | URL help | Help files |
|---|
Service status applicability
Choose a service and add its statuses in order. The first status is where a new task starts; "Complete" in the Task list moves it to the next one. Existing tasks keep the order they were created with.
| Service name | Order | Sub-Task | Next sub-task |
|---|
No status added for this service.
All services and their statuses
| No. | Service name | Statuses in order |
|---|
Leave & termination
An employee asks for leave or termination and chooses who will do his work. That employee must agree first, then you approve here. While a leave runs, the sub-tasks of the employee are with the covering employee and come back after the leave. After the last working day of a termination his work stays with the covering employee and his sign-in, details, notes and drafts are removed.
An urgent request (chosen by the employee, or a normal one with too little notice) is never approved automatically: you decide it here.
No request yet.
| Employee | Request | Dates | Work goes to | Reason | Status |
|---|
Ask for leave or termination
My requests
No request yet.
| Request | Dates | Work goes to | Status |
|---|
Settings
The details you gave at registration. Your logo is shown to your customers, in your dashboard and while the AI answer is loading. The e-mail cannot be changed.
Employees
An employee's name, e-mail, mobile and address are saved in your database. He gets his name, role, e-mail and the password you set by e-mail and signs in with "Employee sign in". He sees only what you tick here, and you can switch him off or on at any time.
No employee yet.
| Name | Role | Mobile | Can use | Status | Last sign in |
|---|
PC access
Employees: allowed PCs
Switch this on and an employee can sign in only from PCs you approve. A new PC an employee uses is listed here as "waiting"; press Approve to allow it. Your own sign-in (e-mail OTP) is not affected.
Attendance
The first sign-in and the last sign-out of each employee for each day of the last 30 days (India time). It fills by itself; nothing to press. If an employee closes the browser or the tab without pressing Sign out, it is shown here too.
No sign-in in these dates.
| Date | Employee | First sign-in | Last sign-out | Time at work | Status |
|---|
Your customers
| # | Business | Mobile | Added | Dashboard |
|---|
No customers yet. Add the first one in Add a customer.