How to use CRM for practical day to day work

I think the fix is to turn the question around. Instead of asking what should go into the CRM, ask what you need out of it at 9:05 on a Tuesday. For me, that means three questions. What needs my attention now? What changed in the customer's situation since I last looked? Who needs to do what next?

Where each kind of information lives

Guides on using CRM software usually skip this part. In Bigin, a contact is a person, and a company is the business they work for. A pipeline record is one piece of work, such as a quote, moving through stages inside a Team Pipeline. Bigin has no separate leads module, so a new inquiry is a contact plus a pipeline record in an early stage.

Around those records sit notes and three kinds of activity. A note records what was said or decided. A task is something a person has committed to do, with an owner and a due date. An event is a meeting with a time, and a call is a logged conversation, answered or not. With email integration, which starts on the Express edition, emails attach to the contact and the pipeline record too. My rule of thumb is that facts about a person go on the contact, facts about a piece of work go on the pipeline record, and any promise becomes a task.

What needs my attention now

On an ordinary morning, four things compete: overdue tasks, new inquiries, callbacks you promised, and customer deadlines. The usual advice is to work the biggest deal first. I disagree. The size of a deal tells you what it is worth, and nothing about what it costs to leave alone for a day.

Here is my order. Commitments to a customer come first, such as a callback you promised for today, because a broken promise costs more trust than anything else being late. Customer deadlines come second, since a bid that closes at noon is gone at 12:01. New inquiries come third, because the person who asked yesterday is comparing you with whoever answers first. Your own overdue tasks come fourth, because an overdue task is a date you chose, and you can renegotiate it with yourself.

What matters for each item is the consequence of delay. A $600 reorder you promised to confirm today outranks a $40,000 proposal nobody expects until Friday.

For daily planning, Bigin puts tasks, events, and calls together in Calendar View, available on trial and paid editions, with filters for activity type, owner, and status. WorkCon, a labor hire and traffic control business based in Brisbane, Australia, uses that calendar as the operating hub for its sales team, and splits its territory into sub-regions so a representative sees one area at a time. The habit is worth copying: decide what you are working on, then look only at that slice.

Figure 1. Four kinds of work compete on an ordinary morning, and this is the order the article argues for, with the question to ask at each step.

Three dates that look alike and are not

A task has a due date. A deal has a deadline the customer agreed to. A record has a time since the last meaningful interaction. Many missed follow-ups begin with treating those as one thing.

The due date on a task is your intention. It puts the task on the right day, and you can move it without anyone outside the business knowing.

The deadline agreed with the customer is a constraint. It belongs on the pipeline record, in Bigin's Closing Date field or a custom date field, because it has to outlive any single task.

Time since the last meaningful interaction is a measurement, and nobody sets it. A conversation eight days ago is not overdue by itself; it is a prompt to decide whether anything needs to happen.

Vancouver Premium Packaging, a custom packaging supplier in Vancouver, Canada, runs quotes through a sales pipeline. If a quote gets no response for seven days, a follow-up reminder is triggered automatically. The company reports that quote-to-deal conversion rose 30% because the team spent more time on existing quotes instead of only chasing new leads. The figure is the company's own and has not been independently measured. The habit is the point: an existing quote got attention because a measured silence crossed a threshold the team had chosen.

The three customer reminders in this article fire on three different triggers. WorkCon's follows an action by the rep: John Anstee, Brisbane Client Engagement Representative at WorkCon, says he has it set to remind him to ring a client two days after he sends off rates. Vancouver Premium Packaging follows the absence of an action by the customer. Naz Law's two-week alert, which I come to below, fires when a record has not changed at all. None of these intervals is a recommendation; yours should match how long your customers normally take to decide.

Figure 2. The three customer reminders described in this article fire on different triggers, and each interval was chosen by that team for its own customers.

What changed in the customer's situation

The note you write after a call or meeting is where most of a CRM's value is created or lost. A weak note reads like this: "Spoke with the customer about the quote. It went well. I will follow up next week." Nothing in it helps the next person.

An improved note reads like this: "The customer confirmed the quantity of 500 units but now needs delivery split across two shipments, the first by October 30 and the second by November 13. The quoted price assumed one shipment, so a revised quote is needed. Next action: I will send the revised quote by email by Thursday, October 15."

The second note records what changed, what was agreed, and the next action with an owner and a date.

Completing a task does not move the customer's situation forward by itself. Marking "Call the customer" complete means you made the call, and the deal may be exactly where it was.

If a call goes unanswered, log it as not answered, create a task for the next attempt, and leave the stage alone, because trying is not progress. A declined proposal goes to a closed lost stage, with the reason written in a note in the customer's own words. A changed requirement means updating the fields that changed, noting what changed and why, and creating a task to requote; the stage usually stays put or moves back, and that is simply accurate. A request to reconnect later becomes a task dated for the day the customer named, with a note on why they asked to wait, and the stage stays where it is unless your pipeline has a waiting stage. A polite "call me next month" feels like progress, and it is not.

Stage transition rules, available on the Premier and Bigin 360 editions, let an administrator require a field, a note, a file, or a checklist before a record moves between two specific stages. They stop "I will add the note later" from becoming "there is no note."

Records that are waiting on someone else

Three things need to survive a wait on a customer, a colleague, or a supplier: who you are waiting on, why, and the date you will look again. In Bigin, that is a note with the reason, a task dated for the review with a name like "Waiting on supplier confirmation," and a stage if your pipeline has one. Vancouver Premium Packaging's prospecting pipeline has a "no reply for 60 days" stage, so silence has somewhere to go.

Two habits cause most of the damage here. The first is sending another follow-up because a task came due, not because anything changed. If the customer said "after the 15th," a message on the 10th is noise. The second is dragging the same overdue task forward day after day. If you have postponed a task twice, the task itself is wrong. Either the date was a guess, so write the real review date, or the action depends on someone else, so rename the task to say what you are waiting for.

Bigin workflows can create a task or send an email a set number of days after a trigger such as a stage change. Bigin's help documentation does not describe scheduled actions being cancelled when the record changes afterward. So if the customer replies on day three of a seven-day wait, review the pending reminder task and close or re-date it yourself. The automation is a prompt, and the decision is still yours.

One quote request followed through four decisions

This example is hypothetical. It is not a Bigin customer story, and the business and figures are invented.

A two-person flooring company gets a call on Monday, October 12, from a customer who wants a quote for 1,200 square feet of vinyl plank in a rental unit, installed before new tenants arrive on October 31. The owner creates a contact, a pipeline record in the "Quote requested" stage with the Closing Date set to October 31, and a task named "Send quote" due Wednesday, October 14.

On Wednesday, she sends the quote, moves the record to "Quote sent," writes a note with the price and the assumption that the unit will be empty, and creates a task named "Call about the quote" due Friday, October 16.

On Friday, the customer calls first. The unit will not be empty until October 24, so the work has to happen between the 24th and the 31st. She updates the record, writes a note with the new window, and creates a task named "Send revised quote" due Monday, October 19. The record stays in "Quote sent" because the customer still holds a quote, just the wrong one. She marks the Friday call task complete, and completing it moved nothing.

On Monday, the revised quote goes out. The customer asks to be called after October 21, so she creates a task named "Call back about revised quote" due Thursday, October 22, and notes the reason for the wait.

On October 22, the owner is out sick. Her colleague opens the record, reads the notes, sees the October 31 deadline and the installation window starting on the 24th, checks that no new email has arrived, and only then calls.

What to leave behind when work moves to a colleague

The person receiving a record needs five things, and all of them can live on it: the current stage and why it is there, the last thing the customer was told, what the customer expects next and by when, any constraint such as "prefers email" or "the owner's partner makes the decision," and the open tasks with their dates.

Before contacting the customer, the colleague should check the most recent email on the record, confirm the deadline still holds, and ask whether any scheduled reminder task still makes sense given the notes. In Bigin, users can mark emails Private or Public, and a private thread will not be visible to the colleague.

Naz Law, a Canadian law firm founded in 2021, works this way. Tasks assigned to clerks appear in their workspace, and the team uses Calendar View for hearings, follow-ups, and pending actions. Syashu Pesswani, Associate Lawyer at Naz Law, describes the effect: "As soon as I assign a task in Bigin, the team can see it immediately. I don't have to separately call or inform anyone." That quote describes how work is organized; a task in a workspace still needs a person to do it. Tulsea, a talent representation agency with 30 people in Mumbai and Los Angeles, relies on notes for the same reason: when an agent is on leave, a colleague reads the notes and carries on with the customer.

In Bigin, the mechanics are a change of Owner on the pipeline record and on each open task, which assumes more than one user. The Free edition is single-user, so a shared handoff needs the Express edition or higher, at $7 per user per month, billed yearly as of today.

What a manager can do with the same records

Activity counts show who was busy. A manager's job is to find who is stuck, and the better questions are which records have gone untouched for longer than your normal decision time, which overdue tasks are piling up on one person, and which records have waited on a supplier or colleague past their review date.

Bigin's filters answer those questions. Custom list views can be shared with selected users, and the Untouched Records time-tracking filter finds records nobody has worked in a chosen period. Tulsea's managers use a writer/director filter to look at one agent's pipeline without a meeting. Naz Law uses an inactivity reminder that notifies the team when a deal has not been updated for two weeks, which prompts a review of that client.

The useful intervention is specific. Reassign the Owner on a record and its tasks when one person is overloaded. Call the supplier yourself when a job has waited three weeks. Checking that each rep made 40 calls is not the job.

A small setup you can test tomorrow

No migration is needed first. Pick five customers you currently owe something to. Create a contact for each. Create one pipeline record per open piece of work, in the stage that matches reality today, with the customer's deadline in Closing Date where one exists. Write one note on each record in the improved format above. Create one task per record with a due date and an owner, and on a multi-user edition assign at least one to someone else.

Then add one reminder rule. Go to Settings, then Workflows, then + New Workflow. Set the trigger to a pipeline record being edited, with a condition that Stage is "Quote sent" or whatever your pipeline calls that stage. Add a scheduled action that creates a task named "Call about the quote" for the record owner three days later. Workflows exist on every Bigin edition, and the Free edition allows three automation rules in total.

Tomorrow morning, open the Activities module, or Calendar View on a trial or paid edition, and filter to your own tasks. Can you tell what to do first? Can you tell what changed on each record without opening email? Can you tell who is doing what? If yes, add five more. If not, the missing piece is almost always a note.

Bigin's Free edition covers one user and 500 records, and every paid edition comes with a 15-day trial, so this exercise costs nothing to run. Start with Bigin and set up those five records today.