Following up an offer without hounding the buyer

An offer is a nervous moment for everyone. The agent who calls too often looks desperate; the one who goes quiet loses the deal to a faster competitor.

The BittaFlow team

3 min read

On this page
  1. The first hour
  2. What to put in writing
  3. The vendor conversation
  4. The counter-offer
  5. How often to call
  6. When the buyer goes quiet
  7. When the vendor goes quiet
  8. Record every version
  9. Where BittaFlow fits

An offer arrives at 6pm on a Thursday. The buyer has been thinking about it for three days, has spoken to a mortgage broker, and is now waiting to hear whether it is accepted.

The agent has a choice: call the vendor now, or wait until morning.

The first hour

Two calls, in this order.

The vendor first. Not to pressure them, but because they should not learn about an offer from a portal notification. Read the offer exactly as it was made: amount, conditions, position, timeline.

The buyer second. Confirm the offer was received, in writing, and say when they will hear. “I’ve put it to the owner this evening, and I’ll come back to you tomorrow by noon” is enough. It is the deadline that stops them worrying.

What to put in writing

Send the buyer a short confirmation:

Thanks Sam. Offer of £X for 14 Bridge Street received at 6:12pm on 14 March. Subject to mortgage and survey. I’ve passed it to the owner and will come back to you by noon tomorrow.

That message does three things. It timestamps the offer, it restates the conditions, and it commits the agent to a reply. All three matter if the deal later gets messy.

The vendor conversation

Most vendors ask one question first: “Is it a good offer?”

The useful answer is not yes or no. It is the comparison:

  • What else has been offered, if anything.
  • What the property was marketed at.
  • How long it has been on.
  • What the buyer’s position is worth. A chain-free buyer at slightly less can be better than a chained buyer at asking.

Then ask what they want to do, and give them a deadline. “Let’s decide by tomorrow lunchtime, so we don’t lose them” is fair to everyone.

The counter-offer

Keep it short and give a reason. “The owner is looking for £X, given the two offers on the table” is a reason. “The owner wants more” is not.

Never invent competition. Buyers talk to each other on forums and in the school playground, and a fabricated rival offer is the fastest way to lose credibility in a small town.

How often to call

The rule: every contact must carry new information or a decision.

  • Day 1: offer received, timeline set.
  • Day 2: vendor’s response.
  • Then daily only while something is moving.

Calling a buyer three times a day to say “still waiting” makes the agent sound anxious, and anxiety is contagious. Silence with a stated deadline is calmer than noise.

When the buyer goes quiet

If the buyer promised documents and did not send them, one message, then one call, then a note in the record. Do not chase five times in two days.

If they have gone quiet after an offer was accepted, that is different. Call, and ask directly whether they are still proceeding. An early awkward conversation is cheaper than a fall-through in six weeks.

When the vendor goes quiet

Same principle. Vendors sometimes freeze because they are unsure, or because they are talking to another agent.

Ask one clear question: “Do you want to accept, counter, or wait?” A vendor who cannot answer that is telling you something.

Record every version

Offers get renegotiated after a survey. If the record only has the final number, nobody can explain how it got there.

Log: amount, date, conditions, who made it, and the vendor’s response, each time. Two minutes of typing saves an hour of argument.

Where BittaFlow fits

BittaFlow keeps the offer as a record with a version history, sends the written confirmation to the buyer, and puts the vendor decision in the same thread as the viewing feedback. The agent can see who is waiting on whom.

Set the deadline in the first message. Then keep every contact worth making.

Useful? Send it to someone who runs the phones.