Cold email lands in spam when you sell to restaurants
Is your last campaign sitting in spam folders right now? Here is how people who sell to restaurants fix it.

Is your last campaign sitting in spam folders right now?
Sending a large blast from a fresh domain is a quick way to end up in spam. Many tools push volume first and leave you to deal with the consequences.
It hits harder when you sell to restaurants. Restaurants run on thin margins and long hours, and the owner or general manager decides on suppliers, software and marketing. Groups have a head office buyer, but independents choose on price, reliability and how little extra work a change brings.
Emails that land in spam are never read, and a damaged sender reputation also hurts your normal mail. Recovering takes time.
Small batches instead of big blasts.
Riftjaw sends campaigns in small batches, so volume stays gentle. You send a test to yourself first and can pause and resume at any moment. Sending goes through the mail setup of your account, and unsubscribed contacts are skipped automatically.
- Fields that fit restaurants, such as cuisine
- Email prefixes that fit, like info@, bookings@, reservations@ and manager@
- Status, tags and a segment on every record

How to fix it in Riftjaw
- Send a test. Check how the email looks in your own inbox before anyone else sees it.
- Start small. Pick a focused segment and let the campaign go out in small batches.
- Watch and adjust. Follow the send log and pause if something looks wrong.

Other walls when prospecting restaurants
Restaurant lists change fast as places open, close and change owners.
Each record keeps its source and date, and you can archive closed places so your active list stays current.
The bookings@ address reaches a host, not the owner.
Tick several prefixes in email from domain, such as info@ and manager@, and note on the contact who replied.
You cannot tell which restaurants you already visited in person.
Set the status to Contacted and add a note after each visit, so the whole team sees it.
Fields worth recording for restaurants
Add these as fields in your lead file. Any column in your import can become a field.
| Field | Why it helps |
|---|---|
| Company name | The key field. Duplicates are checked on it or on the website. |
| Website | Needed to derive an email when the export has none. |
| Cuisine | The type of food shapes which products and suppliers are relevant. |
| Covers | Seating capacity hints at volume and budget. |
| Independent or group | Groups buy centrally, so you need a different contact and approach. |
| Delivery | Restaurants that deliver need packaging and ordering tools. |
| Opening hours | Knowing when they open helps you pick a time to call or visit. |
Questions people ask
Collect restaurants from public listings such as Google Maps or review sites with a scraper, then import the CSV or Excel file. Riftjaw flags duplicates and lets you add a field for cuisine or area.
Many teams do both. Riftjaw keeps phone numbers as fields and email history per contact, so you can tag who to call and send a short campaign to the rest.
If your file has an email column, that wins. If it only has websites, tick the prefixes you want, such as info@, bookings@, reservations@ and manager@, and Riftjaw derives addresses from each domain. Derived addresses are good guesses, not verified, so start with small batches.
Yes. The Free plan runs the whole pipeline on one list with small campaigns, and you do not need a credit card. Move to Pro when you want more lists, segments and bigger campaigns.
Build a database you own
Create your account, import your first list and see it turn into records you can work.
No credit card · cancel any time · your data stays yours






