DarDev sells 20.tn to Tunisian private schools without mass email blasts. Each school contact lives as a Person in Twenty CRM. You research the établissement, write a short personal line in French, preview the message, approve it, then send one intro email. Opens, clicks, and replies create tasks so you know who to call—not another automated drip sequence.
This guide is for sales and outreach staff. You do not configure servers, DNS, or Listmonk. You work in CRM at crm.dardev.net and run workflows whose names start with 20tn —. Technical orchestration is documented separately in 20tn-crm-workflow-orchestration; mail architecture lives in inside-unified-mailer-stack and consent rules in crm-driven-product-lists.
What you are selling
20.tn is DarDev's school management platform for Tunisia—student records, fees, parent communication, and staff workflows at https://20.dardev.net. Prospects were imported from the public ecoles.com.tn directory; each Person represents a contact at a school, linked to a Company record with the school name, city, and level.
You are not importing spreadsheets into a newsletter tool. Cold schools stay consent-unknown until they opt in. That matches how DarDev runs other prospect pipelines under deployed-realities-explained: CRM first, marketing lists later.
Before your first real school
- Open CRM → People (or the 20.tn view if your admin created it)
- Look for Solution = 20.tn, private school where relevant, valid email, Outreach status = Not sent
- Pick one contact—never batch-select dozens for the same day
- Confirm the Company name matches the real établissement you will reference in French
Quality beats volume. Company-wide warm-up targets roughly ten thousand tracked emails per month across products—not three hundred intros from one person in an afternoon. Your manager may set a daily target of three to ten personalized intros; stay inside that rhythm.
Eight steps on every Person record
Work on the Person record in order. Skipping preview or approval causes failed sends and erodes trust with operations.
Step 1 — Research (two to five minutes)
Open the Person and linked Company. Verify school name, email looks real, phone if present, city or governorate. Note something specific—level (maternelle, primaire, secondaire), neighborhood, bilingual program—so your personal line is not generic flattery.
Step 2 — Personalize fields
- Outreach personal line — one or two sentences in French explaining why this school. Example tone: « Nous accompagnons plusieurs établissements privés à Tunis sur la gestion scolaire et les paiements en ligne. »
- Outreach custom subject — optional; leave blank to use the default subject
- Outreach approved — leave off until step 4
Step 3 — Preview (no email sent)
On the Person, open Workflows and run 20tn — preview intro. Check the Timeline: you should see a Queued note with subject and recipient. No message left the building. Fix the personal line and preview again until it reads naturally.
Step 4 — Approve
When the preview looks right, set Outreach approved to Yes and save the Person. This toggle is the human gate—do not flip it early because you are in a hurry.
Step 5 — Send intro
Outreach approved must be Yes before you run 20tn — send intro on the same Person. Timeline should show Sent and Outreach status should move to Sent. If the workflow stops with Invalid configuration or does nothing, approval was missing—preview again, approve, save, retry.
If send fails with a template or delivery error, read Outreach last error on the Person and contact ops. Do not change DNS, SMTP, or VPS settings yourself. Outbound mail uses product sending infrastructure configured by DarDev—not marketing from the corporate @dardev.net inbox domain.
Step 6 — Wait (automatic)
Every fifteen minutes the system checks opens and clicks; every thirty minutes it scans for replies. You do nothing unless a task appears on the Person.
Step 7 — Act on tasks
- Opened mail — call or WhatsApp within one to two days; offer a fifteen-minute demo
- Clicked link (hot lead) — same day; they showed intent
- Reply from school — read in timeline; respond personally; do not send another automated mail
Each task links to the Person with school name, email, and CRM URL in the description. Work clicked and reply tasks first each morning.
Step 8 — Follow-up (optional)
If status is Sent but no open, reply, or phone contact after about three days, workflow 20tn — follow-up may send a second tracked email automatically. If you already spoke to the director, add a note on the Person and ask ops to cancel the scheduled follow-up so the school is not double-contacted.
Daily rhythm
- Morning — CRM tasks: replies and clicks first
- Midday — personalize, preview, and send three to ten new intros
- Afternoon — call schools with opened tasks who have not replied
Rules that protect deliverability and reputation
- One school at a time—run send workflow per Person
- Never bulk cold mail from Listmonk for schools
- Never mark Outreach approved before preview looks right
- Never use retired 20tn PoC workflows
- Cold schools stay consent-unknown until they opt in to marketing
- Product URL in mail is https://20.dardev.net—keep tone professional, not spammy
How schools entered CRM is described in ecoles-scrape-to-crm-pipeline. Product vision and rollout stages are in 20tn-vision-tunisia-schools. When something breaks technically, escalate to ops with the Person link and Outreach last error text.
When something looks wrong
- Invalid configuration on send — set Outreach approved Yes, save, preview, send again
- Live send blocked — operations has not enabled production delivery for your cohort yet
- Open or click never updates — wait fifteen minutes; if still stuck after twenty-four hours, ops checks sync workflows
- Task not linked to person — ops runs a technical patch; you keep selling
Can I select fifty schools and send at once?
No. Send intro runs on one Person at a time. Batch blast hurts deliverability and violates DarDev consent rules documented in crm-driven-product-lists.
Do I need Listmonk access?
No. You work in Twenty CRM only. Listmonk handles tracked delivery behind the scenes; ops configures it on send.dardev.net infrastructure.
What if the director replies off-thread?
Log the conversation on the Person. Reply from your normal sales channel. Do not trigger another automated intro or follow-up without checking status.
Why preview if I already wrote the personal line?
Preview shows exact subject and recipient in Timeline without sending. It catches typos, wrong school names, and missing approval before a real inbox sees the mail.
How is this different from Hesabi accountant outreach?
Same CRM-first ethics, different product. Hesabi is fiscal software for Tunisian SMEs. 20.tn is school management. Both stay Tunisia-focused; neither spams cold imports into newsletters.
