> For the complete documentation index, see [llms.txt](https://cyberpassion.gitbook.io/internal-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cyberpassion.gitbook.io/internal-docs/tele-calling/process-flow.md).

# Process Flow

## 1. Daily Calling Target

* Complete **75 successful client interactions** every working day.
* Focus on **actual communication** with prospects (not just dialing).
* Record important calls and **share the audio recordings in the WhatsApp reporting group** as proof of communication.

**Daily Target:** 75 Conversations

## 2. Demo Scheduling

Every telecaller must schedule a minimum of **5 product demos for the next working day**.

#### Before Confirming a Demo

* Explain the product briefly.
* Confirm the customer's availability.
* Ensure the customer is interested in attending the demo.

## 3. Demo Confirmation Process

After fixing the demo time:

* Confirm the date and time with the customer.
* Immediately send a **WhatsApp confirmation message** containing:
  * Customer Name
  * Demo Date
  * Demo Time
  * Meeting Link (if applicable)
  * Contact Person Name
  * Support Contact Number

This ensures the customer has all required details before the meeting.

## 4. Demo Timing Guidelines

* All demos should be scheduled **after 10:00 AM**.
* Avoid scheduling demos before 10:00 AM unless specifically approved.
* Maintain sufficient time between demos to avoid delays.

## 5. Post-Demo Follow-up

Immediately after every demo:

* Record the customer's feedback.
* Identify the customer's level of interest.
* If interested:
  * Share pricing details.
  * Connect the customer with the sales team (if required).
  * Continue follow-up until closure.
* If not ready:
  * Schedule the next follow-up date.
  * Maintain regular communication.

**Goal:** Convert every qualified demo into a paying customer.

## 6. End-of-Day Reporting

Submit the daily report **before 04:45 PM**.

The report should include:

* Total Calls Attempted
* Total Successful Conversations
* Demos Scheduled
* Demos Completed
* Interested Customers
* Follow-ups Scheduled
* Sales Converted
* Pending Leads
* Remarks (if any)

Start Day\
│\
▼\
Call Prospects (75 Conversations)\
│\
▼\
Identify Interested Customers\
│\
▼\
Schedule Demo (Minimum 5)\
│\
▼\
Send WhatsApp Confirmation\
│\
▼\
Conduct Demo (After 10:00 AM)\
│\
▼\
Collect Feedback\
│\
▼\
Share Pricing & Follow-up\
│\
▼\
Convert to Customer\
│\
▼\
Submit Daily Report (Before 04:45 PM)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cyberpassion.gitbook.io/internal-docs/tele-calling/process-flow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.