# Sales activity, routes, visits, and evaluation

Section: Selling. Address: https://vende.id/docs/jualan/sales-keliling?lang=en

Sales people visit customers and new contacts, check in and out on their phone, and the owner judges the activity through the KPI and AI Evaluate.

Sales activity is the feature for sales people who work in the field. In Vende every visit is recorded on the sales person's phone: check-in, the stock on the customer's shelf, photos, and the result. When Sales Orders is on, the sales person also takes orders in cartons or pieces, and each order becomes a sales order in their name. The feature used to be called Travelling sales; shops that already use it keep it with their data intact.

This is an extra feature and only needs the **Sales** feature to be on. If its menu is missing, contact the Vende team to switch it on.

The basic part (routes, visits to customers, shelf photos) is always there. The other parts stay hidden until you switch them on in **Settings → Sales Activity**: the sales KPI, contacts and visit purposes (with Evaluate), and a required check-out. Switching a part off only hides it; its data is not deleted.

## Setting up a route

1. Open **Master Data → Sales Agents**, make sure the sales person exists, and fill **Linked user** with the account they log in with.
2. Open **Master Data → Sales Routes**, then press **Create Sales Route**.
3. Fill the route name, choose the **Sales** person who runs it, and tick the **Visit days**. No day ticked means the route runs every day.
4. In **Customers on the route**, press **Add customer**. The order here is the visiting order on the phone. Drag to change it.
5. Save. An inactive route does not show on the sales person's phone.

## Visiting customers on the phone

1. The sales person opens **Transactions → Today's Visits**. The **Today's route** tab lists the customers in route order.
2. Press **Check-in** on the customer being visited.
3. Choose the result. When Sales Orders is on: **Order** or **No order**, with the order in cartons or pieces and a reason when there is no order (the reason **Other** needs a note). When Sales Orders is off: **Meeting**, with a note on the result. Shelf stock and a shelf photo are optional.
4. Press **Send visit**.

A customer who is not on today's route can still be visited with the **Find customer** box.

Without a signal the visit is kept on the phone and sent by itself when the signal returns. A visit that has waited unsent for more than 72 hours cannot be sent any more and has to be recorded again. A visit that was refused is marked **Needs fixing**: fix it and send it again.

Forgot to check in? When you switch on **Contacts and visit purposes** or **Required check-out** in **Settings → Sales Activity**, there is a **No check-in** button next to **Check-in**. The sales person writes the visit down afterwards and must fill in **Why no check-in?**. The time kept is when they wrote it, with no location. Such a visit is flagged **Without check-in** in the list and is judged by Evaluate. A shop that only uses the KPI does not see this button.

## Check-out

When **Required check-out** is on in **Settings → Sales Activity**, the send button on the phone reads **Check out and send visit**. The time the sales person taps it is kept as the check-out time, so they fill in the result while still there and tap it when leaving. A finished visit without a check-out is flagged in the **Sales Visits** list and is judged by Evaluate. A visit written down without a check-in has no check-out.

## Contacts: people who are not customers yet

Switch on **Contacts and visit purposes** in **Settings → Sales Activity**. A contact is someone who is not a customer yet, such as a petrol station guard, an insurance agent or another distributor's sales person, recorded without making a fake customer. Sales people pick or add a contact right on the phone, and you tidy the lists on the computer screens **Transactions → Sales Contacts** and **Master Data → Visit Purposes**.

### On the sales person's phone

1. On the **Today's route** tab there is a **Relations** card. Type part of the name of the contact met and pick it. For someone new, choose **Create new** and fill in the name (required), role, WhatsApp or phone number, and who introduced them (picked from the existing contacts, optional).
2. Press **Check-in**. The phone's location is taken as on a visit to a customer.
3. Pick the visit **Purpose** from the list. If it is not there, choose **Other purpose...** and type its name; it is in the list after the visit is sent. For a visit to a contact the purpose is required. For a visit to a customer it can be left empty.
4. Fill in a note, take a **Photo together** (up to 3), then press **Send visit**. The result is always **Meeting**.

All of it goes through the same weak-signal queue as a visit to a customer: written on the phone first and sent by itself when there is signal.

- A contact holds a name, role (free text), WhatsApp number, and who introduced them (another contact or a customer).
- The **visit purpose** is picked from a list. In **Master Data → Visit Purposes** you add, rename or switch off purposes. A purpose that a sales person sends in through the system is available at once. A purpose is never deleted because older visits keep it.
- The result of a visit to a contact is a **Meeting** with a note. A visit to a contact never becomes an order.
- **Transactions → Sales Contacts** shows every contact, who introduced them, how many people they introduced and how many visits they had. **Make customer** creates a new customer from the contact (name and number); the visits and the chain of introductions stay.

A sales person only sees the contacts they met themselves, unless they may see all visits.

## Bell reminders

When the sales KPI is on, the bell sums up the month's KPI every morning for whoever holds **Sales KPI**. Two reminders are about a quiet sales person, with their limits in **Settings → Alerts**, section **Sales KPI**:

- **Sales Agent Not Visiting**: a sales person who has not visited (a customer or a contact) for this many working days in a row up to yesterday. The default is 3 working days.
- **Sales Agent Not Selling**: a sales person with no sale in their name for this many working days in a row up to yesterday, counted from their last sale (or from the day their Sales record was made if they never sold). Only for sales people whose login is linked to a Sales record. The default is 3 working days.

A sales person who does not sell but visits a lot only gets the second reminder, so you can ask what is in the way without judging them lazy.

## Sales orders need an admin to accept them

By default an order from the sales phone becomes an **Open** order at once. When the shop wants an admin to look at the stock first, whoever holds the **Settings** role turns on **Orders from sales need an admin to accept them** in **Settings → Sales**, section **Orders from Sales**. A shop that does not turn it on is unchanged.

While it is on:

1. An order the sales person sends becomes an order **Awaiting review**. Its stock is not booked yet, and the admins who may accept orders are told in the bell.
2. An admin opens it from the bell, from the **Dashboard** section **Orders from buyers** (source **Sales**), or from the **Awaiting review** tab in **Transactions → Sales Orders**. On the order's page, the section **Stock for This Order** shows the stock of each item and whether it is **Enough**.
3. Stock is enough: press **Accept**. The order becomes **Open** and its stock starts to be booked. For a sales person limited to stock, accepting is refused when other orders have used the stock: Vende names the short goods, then wait for stock or **Reject**. A quantity must change because stock is short? Press **Accept**, then **Edit** on the order's page.
4. The order cannot be met: press **Reject** and write the reason. The order becomes **Cancelled**.
5. The sales person is told in the bell (with the reason when rejected). In **Today's Visits**, the visit shows the order number with its status, for example **Awaiting review** or **Cancelled**.

A waiting sales order does not expire like a buyer's order: it waits until an admin answers. Whoever may change sales orders (Head Cashier) may accept or reject. See [Order statuses](https://vende.id/docs/jualan/pesanan-penjualan?lang=en#order-status).

## Seeing the results

- **Transactions → Sales Visits**: each visit with its customer or contact, purpose, result, check-in and check-out time, location, and the **Without check-in** flag.
- **Reports → Visits per Sales Person**: visits, orders, meetings, and reasons for no order per sales person.
- **Reports → Sales KPI** (when the sales KPI is on): EC, NOO, RO, and AO per sales person. See [Sales KPI](https://vende.id/docs/laporan/laporan-penjualan?lang=en#sales-kpi-ec-noo-ro-and-ao). When contacts are on there is an **Activity** table: visits to contacts, new people, introductions given, contacts who became customers, orders, working days without a sale, and **activity points**. Points are each of these times its weight, which you set in **Settings → Sales Activity**.

A sales person who does not sell but visits steadily and brings in new contacts shows in the Activity table, so the effort can still be recognised.

## Evaluate with the AI

When contacts are on, **Reports → Sales Evaluation** has an **Evaluate** button. Pick the sales person and the period. The sales person's visits are sent to the AI (the Sonnet model; the lightest model is not used because it is too light to judge notes) and the result is kept:

- **What is odd**: for example the same location again and again, notes that repeat or sound careless, hours that make no sense, or figures that look too good.
- **What is worth asking**.
- **What deserves praise**.

Each finding gives its reason and links to the visits it is about. Treat the result as something to ask about, not a verdict: check with the sales person before concluding. One evaluation uses one question of the shop's daily AI allowance; when the allowance is used up or the AI is unavailable you are told and the allowance is not used.

## Orders become sales orders

When Sales Orders is on, the office opens **Transactions → Sales Orders**. The visit orders are there in the sales person's name. Stock and the credit limit are checked again when the order becomes a note. If stock is short or the credit limit would be passed, the order is still saved and the sales person is told. See [Recording sales orders](https://vende.id/docs/jualan/pesanan-penjualan?lang=en).

## How field sales KPIs are usually measured

Distributors in Indonesia usually judge field sales from a mix of activity and result figures: visits per day, **EC** (visits that produced an order), **NOO** (new outlets opened), **RO** (existing outlets that ordered again), **AO** (outlets that actively buy), and achievement against the sales target. Vende calculates all of them in the Sales KPI. For sales people whose first job is to build relationships, the Activity table adds measures that apply before any sale: new people met, introductions given, and contacts who finally became customers.
