See it first
A draft and a workspace, on this page, without signing in.
Open the demoBeacon · CRM by Wilken
The relationship, kept in one place.
Beacon is a CRM for teams that sell. It takes the manual work off contacts, email, calls, and the next step. A draft is ready. The person who owns the relationship sends it.
Lena Berg
- Mail Draft is ready. Not sent.
- Call Transcript in. Task: call back Thursday.
- Sequence Stopped. She replied.
The usual mess
The follow-up lives in five tools.
A spreadsheet, an inbox, a notebook, and a call that nobody wrote down. In Beacon the next person opens the contact and sees where things stand.
Nothing sits on the contact
The last email is in one place, the promise from the call in another. The next person starts again.
The next step is a guess
Someone meant to write back. The sequence does not know. The contact hears from two people.
Channels do not meet
A field visit, a mailbox, and a phone call should be one timeline. In most setups they are not.
A no stays in one place
The address is out of this mailbox. In the other workspace the sequence is still sending.
Platform
The contact, and everything around it.
What is actually in Beacon. No module that exists only on a slide.
What you work in
One workspace per brand. The list matches the navigation and the settings.
Contacts, companies, deals, leads
One workspace per brand. Roles decide who sees and who sends. Leads share the contact, with their own fields.
Fields, pipelines, labels
Custom fields, deal stages, lost reasons, and labels are set per workspace. Sparse fields do not block import or send.
Sales inbox
Mail goes out from the connected mailbox. The reply address is that person, not a shared alias.
Sequences that stop
A reply, a suppression, or a legal-severity answer pulls the contact out, in every workspace of your brands. A person approves a sequence before it sends.
Calls on the contact
The call is recorded, transcribed, and turned into notes and tasks. You arrange consent. Beacon does not announce the recording.
Drafts, not autopilot
Beacon writes the draft. A person sends it. Your content is not used to train a model of our own.
Field day
A route from the office, the stops worth making, and the note on the same contact when you have been there.
Import
CSV with column mapping and the workspace’s own fields. Suppressed addresses are skipped at import.
Enrichment and groups
Profiles get filled in, and contacts get grouped. A person approves a group before it is used to send.
Suppression
One list for every workspace, plus a list per brand. Enforced at import, enroll, and send. Legal-severity holds cannot be overridden.
Assistant
Help inside the CRM. Sequence and group approval stays with a person. Assigning a contact does not wait for that approval.
Open work
What is still open sits on the dashboard. Alerts stay in the app, per workspace.
Product
What Beacon looks like
Two views: the mail waiting to go out, and the workspace of a brand.
The draft
The mail is written. Mara edits it and sends it herself. Nothing goes out on its own.
Draft · not sent
Thursday at 10 still works?
Hello Ms Berg, thank you for the call today. I will phone you on Thursday at 10. I will send the offer documents ahead of that.
The workspace
One brand, one navigation. What is open today: replies, a sequence waiting for approval, stops on the route.
Berg & Partner
Open replies
4 waiting in the inbox
Sequences
1 waiting for approval
Visits today
3 stops, route is set
Before and after
One contact. The next step is written down.
The old way Copy the thread into a spreadsheet by hand.
With Beacon The thread, the call, and the draft sit on the contact.
The old way Hope someone writes down the callback.
With Beacon The call is logged, and so is the next step.
The old way Send the sequence even to suppressed addresses.
With Beacon A suppressed address stays out of the sequence.
A working day
Three places where it usually falls apart
Scenes from the product.
How it starts
Three steps, on the contact.
- Open the draft
- Look through the workspace
- Name the brand
- Invite the people who may sign in
- Match the mail
- Send the draft
- The sequence stops
In practice
The usual snags, and what Beacon does
For someone deciding. The longer answers are in the questions below.
How does a sequence actually stop?
A reply, or an address on the suppression list, pulls the contact out at once, in every workspace of your brands.
See the demoWho sends the email?
Beacon writes the draft. The person who owns the contact edits it and sends it from their connected mailbox.
See the demoWhat happens to a no?
The global list holds for every brand. A legal-severity reply is added there, and the sequences stop. A workspace admin cannot override that hold.
See the demoQuestions
Before you ask for access.
Can I buy Beacon on this page?
No. There is no checkout and no price on this page. Access is agreed with Wilken, then we open a workspace.
Who is the controller of my contacts?
You are. Wilken processes that data on your instructions under the Beacon Data Processing Agreement. Wilken is the controller of the contract data of your users and of the global suppression list.
Where is the data stored?
Production data and files are in Frankfurt. Some features use processors, including outside the EU. The subprocessor list names them.
Does Beacon announce that a call is recorded?
No. You need consent or another legal basis before a recorded call. Beacon can suspend calling for a workspace if that basis is missing.
Does Beacon send email on its own?
No. It writes a draft. A person reviews it and sends it from the connected mailbox.
Demo
See a contact before your workspace exists.
The demo on this page shows a draft waiting to be sent, and the workspace around a brand.