Skip to Content

CRM that helps you continue working with customers

We organise enquiries, agreements and the team's next actions. We connect sales to real work: a booking, group enrolment, order or project. A pipeline record should help an employee, not become another place for manual reporting.

Discuss enquiry handling

What your company gets

Enquiries are not lost.

Staff can see the source of a request and the next step.

Roles remain distinct.

Contacts, buyers, payers and delivery staff are not merged because of one email address.

Stages represent actions.

Proposals, orders, delivery and payment have different confirmations.

The team can continue the process.

CRM helps hand work over and return to customers for an appropriate reason.

An enquiry needs an owner and a next action

Distinct roles linked to the same enquiry

Organization

The company and its context.

Buyer or contact

Discusses the request and agreed next action.

Payer

Receives agreed financial documents; payment is a separate fact.

Learner or service recipient

Receives only the assigned service and permitted information.

Owned enquiry or order

Link roles and context; do not merge identities or access automatically.

A lost contact or repeated enquiry needs a separate check. An enquiry, an accepted proposal and a real payment are different events; support for one messenger proves nothing about another.

Agreed scope and delivery checks

What we work on

  • Map enquiry handling, sales stages and team responsibilities.
  • Configure records, stages, tasks and access for everyday work.
  • Connect incoming enquiries and relevant systems without unnecessary duplicate entry.

What you take away

A CRM workflow the team can follow, with clear ownership, tested permissions and useful customer records.

How we work

Understand

Review how enquiries are received and followed up today.

Agree

Agree stages, required information, roles and handover points.

Build

Configure the workflow and connections for a focused first scope.

Verify

Test realistic cases with the people who will use the system.

Our approach →

When context gets lost between people and applications

A request arrives through the website, details remain in email, the proposal sits with a manager and the delivery team receives only a short comment.

The customer repeats information while the team cannot see current terms or an owner.

We examine this handoff and define the minimum useful data.

We do not migrate every field from an old spreadsheet simply because it was there.

What we configure

Receiving and assigning enquiries

We define sources, necessary context and assignment rules.

Every request has an owner and next step. A confirmed intake channel is not called a universal inbox for every messenger: each source is checked separately.

Contacts and roles

We distinguish the organisation, contact, buyer, payer and service user.

A matching name or email can help search but is not enough reason to merge people and their histories. Ambiguous matches are referred for review.

Stages with clear meaning

Together we define what is needed for a transition: a scheduled consultation, confirmed requirements, accepted proposal version or placed order.

A stage should not mean different things to different employees.

Handover to delivery

We connect an accepted agreement to a booking, group, project or order.

Changes in scope and terms return for approval. A sale is not considered delivered simply because a card moved to the last column.

Follow-up and reporting

We configure tasks, useful reminders and selected measures.

We distinguish enquiry counts, suitable requests, accepted proposals and actual payments. A report should support decisions rather than hide quality behind a total card count.

At an academy, the corporate buyer, payer, group administrator and learner may be different people.

At a supplier, the contact, purchaser, engineer and person approving a proposal make different decisions. At Beauty, one email does not mean the treatment histories of two people can be merged automatically.

Therefore pNet configures more than CRM fields: it defines identification rules, stages and responsibility, including who confirms a request, who can access commercial information, what constitutes approval and on what basis the next contact is permitted.

Received, agreed and paid retain distinct meanings.

We connect the website and portal, data exchange and marketing analytics only for the selected chain.

This helps verify useful outcomes without mixing contacts and financial events.

All pNet business systems.

An enquiry record before handover

Illustrative record · not a completed client project
Customer roles
Buyer, payer and recipient are separate roles
Responsible person
The employee who owns the next action
Next action
Clarify the programme and cohort or the proposal version
Handover basis
An accepted scope or confirmed order, not any correspondence
Identity and payment
A matching email proves neither identity nor payment

How this looks in different businesses

At an academy, an enquiry is linked to a programme and specific cohort; an employer's interest is not an assigned learner place.

For a supplier, configuration and proposal version matter; sending a proposal does not prove acceptance. At a service company, a project begins with agreed scope, not any customer correspondence.

These differences determine fields, stages and actions.

We do not transfer an identical pipeline between industries without checking.

pNet's work

Understand the enquiry journey.

We check sources, customer types and manual handoffs.

Agree stages and permissions.

We assign owners and criteria for transitions between states.

Configure connections.

We use standard CRM and add only the necessary exchange with other systems.

Test real situations.

We examine a new enquiry, repeat contact, rejection and handover to delivery.

We train the team to work with agreements and exceptions.

After launch we help refine the process, improve data quality and develop necessary automation. AI can draft or find context, but should not independently change price or commitments or send a proposal without agreed rules.

Frequently asked questions

What do we agree before work starts?

Data cleanup, imports, integrations and reporting are agreed separately. A CRM process needs clear ownership and consistent use by the team.

What should I share to get started?

Describe your systems, the problem and any known constraints. You do not need a complete technical specification. Please leave passwords, keys and customer data out of your message.

Do we need to replace our current CRM?

No. We first check the process and current system's capabilities. Rules, configuration and one necessary connection often solve the problem.

Can all enquiries be combined automatically?

Only under verified rules. Different people, shared addresses and repeat enquiries require careful identification; otherwise history and access become mixed.

Can tasks be assigned automatically?

Yes, for clear events and conditions. We first define exceptions, an owner and how to correct an incorrect assignment.

Will CRM show exact revenue?

Only with an agreed source of financial data and metric definition. The total value of prospective deals is not the same as invoices issued or money received.

Let's start with one enquiry

Tell us how a request arrives and what happens through delivery. We will find the handoff where context is lost and suggest a useful first step.

Discuss enquiry handling