FunnelRover is built around a handful of words that come back on every screen. Understanding them once saves most of the questions.

The organisation and the roles

Your organisation is your space in FunnelRover: your data, your users, your settings. No other organisation can access it, and one account can belong to several organisations.

What each person can do depends on their role:

Role	Who	What they can do
Admin	The organisation's administrator, usually the contract signatory	Everything, without restriction
Master Data (MaDa)	The person who maintains the referentials	Territories, institutions, users, imports, approvals, cycles, and a view over the whole organisation
Supervisor	A member who manages at least one person	Field work, plus a view over their team and the review of what it submits
Member	Sales rep, seller, promoter…	Field work, limited to their territory

The position describes each person's place in your org chart (rep, area manager, regional director…). You name it freely.

The territory, source of scope

A territory is a part of the field entrusted to one person, its holder. Territories form a tree: a region contains areas.

The territory, and the territory alone, decides what each person sees. A member sees the institutions, contacts and points of sale of their territories; a supervisor, those of their whole team. Moving an institution to another territory hands it, with all its contacts, to the new holder.

When a holder is away for a long time, an interim hands their territory to a colleague for a dated period, without taking it away from them (see CORE).

The people you visit

Institution — an establishment: hospital, clinic, pharmacy, wholesaler, school… It has a type, a class and a rank, three independent axes you define.
Contact — a person, usually attached to an institution. A CRM contact is part of your field portfolio; a lead (or 1PD) comes from a form, a quiz or an event and waits to be qualified before entering planning.
Point of sale — a retail outlet tracked for visibility and distribution (REACH module).

The rank, which sets the pace

A contact's rank says how often to see them: for example "A: once every 30 days". It is what computes the number of visits a cycle plan schedules. An institution's rank is used to choose which institutions a plan covers.

The cycle and the plan

Cycle — a dated period of field work (often a quarter), opened by the MaDa, with its working days and number of visits per day.
Cycle plan — what a rep plans to do during the cycle: their days, and in each day their slots, one contact per slot. They generate it, submit it to their reviewer, then carry it out.
Coverage — the share of past slots that led to a visit. A past slot without a visit is overdue: missed if it carries a reason, silent otherwise.

Absence and consent

An absence is declared at once, without asking anyone's permission; it changes the figures only once confirmed by the reviewer. The days of a confirmed absence no longer count in capacity, and their slots no longer count as overdue.

A contact's consent is kept per channel (email, WhatsApp) and dated. No marketing message goes to a contact who has not consented on that channel.