No.
You don't need a CRM. You need one notebook for every inquiry, and a WhatsApp habit.
What's really going on
Leads land in three places: WhatsApp, your phone, and your doorway. The problem isn't tracking — it's that walk-ins and calls never get written down, so you forget to follow up. WhatsApp already remembers itself. The other two don't. That's where appointments slip.
What to do instead
- WhatsApp Business app (free) — turn on Labels. Tag every chat: "New", "Booked", "Showed up", "No-show". That's your pipeline.
- Google Sheets (free) — one tab, six columns: date, name, phone, channel, appointment slot, status. Every walk-in and phone call goes here before they leave or hang up. WhatsApp ones too, once a day.
- Habit: end every day with a 5-minute scan. Anyone in "New" with no reply gets a WhatsApp message now.
First action, do it in the next 30 minutes: open WhatsApp Business, go to Settings → Business tools → Labels, and make those four labels. Then open a blank Sheet and type the six column headers.
What you're being oversold
Someone will pitch you AiSensy or Wati for "WhatsApp automation." At 10–50 inquiries handled by one person, broadcast tools and chatbots are noise — you can reply faster than a bot can qualify. Freshsales is overkill for a solo shop. Skip them until you have staff or hit ~100 inquiries a month. Doing nothing isn't free, though — every forgotten walk-in is an empty slot you could have filled.
When to revisit this
The day you hire someone who also needs to see the inquiries, or the week you cross 80 inquiries and the sheet starts feeling heavy.
The part worth getting right
The judgment call is whether your walk-ins and phone calls actually get written into the sheet — because if they don't, no tool fixes it. If you're disciplined enough to log them in the moment, the sheet plus WhatsApp labels will carry you for a year. If you know you won't (busy counter, hands full, customer in front of you), the fix isn't a CRM — it's a one-tap WhatsApp shortcut so even walk-ins get added to a chat thread you'll see later. Same problem, different fork. Which one is you?