VOGO® eBS CRM
You know who you work with, what you wrote to each other and what you sent them — and the e-mail campaigns and event registrations go straight into the same records.
EUIPO EUTM 019103505VOGO® eBS CRM is the record of the organisation’s relationships: the people and companies you work with, what you wrote to each other, which campaigns they received e-mails from and which events they registered for. Everything sits on the contact, not scattered across colleagues’ mailboxes and spreadsheets.
E-mail campaigns go out from the same records, through the provider you choose, and every e-mail sent, failed or replied to stays visible. Registrations on the event pages become contacts, with their company, without any manual copying.
One contact. Its whole history. The same records for the whole team.
Every contact has its company, and the company is a third party of the organisation — the same one used by the registry and the documents. Labels are added and removed right in the row, and the table keeps its columns, order and widths for each user.
The contact details, the company as a third party of the organisation, the labels and, on the right, the correspondence and the lists the contact belongs to. Received and sent e-mails are attached here, with the original file, so anyone opening the record sees what was said.
For every campaign: the subject of the e-mail, how many recipients received it, how many failed, how many are waiting and who replied. The exact e-mail each recipient received can be rebuilt at any time.
Workshops, online conferences and meetings, each with its public registration page. Whoever registers becomes a contact, with their company, and appears straight away in the list of registrants.
Six screens, each for one step of working with contacts: from bringing them into the records to the campaign sent and the event closed.
The people and companies the organisation works with: contact details, position, city, the company’s main contact, labels, correspondence.
From the Excel file made after the downloadable model, from a pasted list or from free text, from which the addresses are extracted.
The subject and body of the e-mail, with alternating variants, attachments and fields filled in for each recipient.
The recipients chosen by filters or from a list, the template and the start of the campaign, with a preview and a test e-mail.
All campaigns, with their recipients, the status of every e-mail, the waves and the replies received.
Workshops, conferences, discussions and meetings, with their registrants and the status of each: registered, attended, cancelled.
The e-mail is prepared once, goes out to every recipient with their own data, and the campaign keeps track of everything that happened.
The time the e-mail left for the recipient.
The reason, so that the address can be corrected.
For campaigns in waves, the e-mail received back from the recipient.
The contact no longer receives campaign e-mails.
The workshop, the online conference or the meeting has its own public registration page, and the registrations go straight into the CRM.
The form on the event page creates the contact, with their company as a third party of the organisation, and adds them to the event. The organiser receives the registration e-mail, and the records are already complete.
Everything below works in the application today; none of it is an intention on the roadmap.
A contact’s company is a third party of the organisation, the same one the registry and the documents use. There is no second list of companies.
Coloured labels, added and removed right in the row, on one contact or on several at once; the table filters by them.
Text that changes with the recipient’s data — “if the city is…, then…” —, used in the subject and in the body of the e-mail.
Several variants of subject and text in the same template, alternated between recipients.
Sending through Brevo, MailerSend or the organisation’s own SMTP server, with the e-mails-per-minute limit you set.
The campaign carries on by itself on the server; it can be stopped, resumed and sent again to those who did not receive it.
Every e-mail carries the unsubscribe link, including unsubscribing straight from the recipient’s mailbox (RFC 8058).
A document shared with a PIN gets, in each recipient’s e-mail, a PIN of that recipient only; you know who opened it and when.
Everything done in the screens can also be done from an external system, with the same OAuth 2.0 token as the document services.
Each organisation’s data is kept apart; access is granted by role, and every call to the service is logged.
The provider chosen by the organisation: Brevo, MailerSend or its own SMTP server. The sending settings belong to the organisation, and passwords and keys are no longer displayed once saved.
Yes. From the Excel file made after the import model, from a pasted list or from any text, from which the e-mail addresses are extracted. Existing addresses are not duplicated.
The contact is marked as unsubscribed and no longer receives campaign e-mails. Unsubscribing works both from the link in the e-mail and from the button the recipient’s mailbox offers.
For campaigns sent in waves from the mailbox, yes: each recipient’s reply appears on the campaign. Any e-mail received can also be attached to the contact, in their correspondence.
Yes, through the REST web services: contacts, campaigns, templates, events and settings, with an integration client of the organisation and an OAuth 2.0 token. The application’s own screens use these very services.
Yes. A contact’s company is a third party of the organisation, the same one used in the registry and in the documents, so its data is kept in a single place.
In a demo we bring part of the contacts you already have into the records, prepare a campaign and an event, and you see how it all looks on a contact.
VOGO® eBS CRM
Part of VOGO Enterprise Business Suite · the same companies, rights and web services as the rest of
the application.
Note: The services are provided in line with the European DNSH principle – “Do No Significant Harm”, in accordance with Article 17 of Regulation (EU) 2020/852 on the establishment of a framework to facilitate sustainable investment and with the European Commission’s technical guidance on the application of the DNSH principle, C/2023/111.
