Find answers.
Learn faster.
FAQ, practical guidance and the most important topics collected in one place.
Frequently asked questions
Answers to common questions about using Oroom.One.
You pay a subscription for scale, a one-off fee for the launch, and separately only for SMS and WhatsApp. Every plan includes all platform features, and contacts and emails are unlimited (to your own database with consents).
• Choose the plan by the higher of two thresholds: the number of products in your catalog or the size of your team. The plans are Start, Growth, Pro and Enterprise, from PLN 299 net per month.
• Implementation is a one-off fee depending on the scope: Standard (launching the instance and connecting your store or product source), Onboarding PRO (training on top) or Onboarding Enterprise (integrations and changes for your process, after a pre-implementation analysis).
• You can also buy support (hours of the Oroom team per month) and SMS packages; WhatsApp is billed at Meta rates.
Current prices, plan limits and implementation scopes are on the Pricing page. If you are not sure which plan to choose, book a short presentation and we will match it to your catalog and team.
More: oroom.one/en/pricing
No. The best results come from starting with one process that limits your sales most today and adding modules in stages. Examples of a first step:
• product offers for salespeople – an offer from the catalog under a link, tracking when the customer opened it, and a call at the right moment,
• order in leads – forms, consents, owners and an automatic welcome email,
• communication automation – reminders, follow-ups and tasks for the team.
You can also start with a pilot: a selected group of salespeople and one sales process. The pilot results help plan the next stages. All features are available in every plan, so expanding does not require a new tool or paying for modules – you change the plan only when your catalog or team grows.
A product offer is a personalized proposal for a specific customer, published under a link as a page – instead of a PDF attachment. It contains products from the catalog with quantities, individual prices and discounts, a validity date and sections: description, video, gallery, FAQ, attachments, salesperson contact and decision buttons. After sending, you see what the customer does with the offer, you can negotiate terms and lead to acceptance and payment.
There are three roles in an offer:
• Buyer – the lead the offer is for,
• Salesperson – the person shown to the customer as the contact (a content creator profile),
• Owner – the panel account responsible for the offer.
A catalog offer (Offer and content → Offers list) is something else: an item in your company's offering, for example a service, training or webinar, with a registration form, certificate and initial funnel. Deals are created from it, while a product offer is a document for one customer.
Where in the panel: Offer and content → Product offers
Oroom records the customer's actions on the offer and shows them in several places:
• in the offer – the “Customer activity” section: number of visits, total time on the page, maximum scroll, last visit and language, button clicks (CTA), video viewing (time, percentage, watched to the end) and the engagement level, for example “High”,
• in the offer – “Product offer history”: a timeline of events from creation through sending to the customer's decisions,
• on the Dashboard – “Product offer events” from all offers: offer opened, file downloaded, offer forwarded to another person (with the recipient's address), CTA click, video watched, contact request, negotiations.
How to use it: several visits, scrolling to the end or forwarding the offer is a good moment for a call. Remember, though, that activity alone does not decide the purchase – treat it as a hint for the conversation.
Where in the panel: [product offer] → Customer activity / Dashboard → Product offer events
A workflow is a scenario that performs steps by itself after an event occurs. It consists of:
• a trigger – the event that starts it (for example “Lead created”, “Product offer sent”, “Deal stage changed”),
• conditions – who it should work for (for example only leads with Polish as the contact language),
• actions – what should happen (send an email, SMS or WhatsApp, wait, add a tag, create a task, update data), with Yes / No branches.
Most often companies automate:
• customer communication – welcoming a new lead, offer reminders, confirmations, follow-ups,
• handling inquiries and purchases – tasks for salespeople, assigning an owner, tagging, reactions to acceptance, payment or rejection of an offer,
• bookings and orders – confirmations, reminders, status changes.
Create scenarios in Automation and communication → Workflows and organize them in groups (for example “New lead”, “Product offer”). The list shows the state of each scenario and the result of its last run.
Where in the panel: Automation and communication → Workflows
Oroom One has tools that help you protect data and communicate in line with the GDPR:
• Consents – you define consents (for example data processing, email marketing, SMS, WhatsApp, terms of service), collect them in forms and surveys, and see the status of each consent with acceptance and withdrawal dates on the customer card.
• Sending only where allowed – campaigns have an option to send only to people with consent, marketing templates have an opt-out button, and automations can check consents in their conditions.
• Secure login – two-factor verification (2FA), passkeys and control of active sessions.
• Access control – user accounts with deactivation, mailbox visibility (shared or private), permissions and an operation history for MCP connections.
• AI – the panel saves only AI usage metadata, without prompt or response content.
Data processing terms are set out in the agreement, and the Enterprise plan offers an individual data processing agreement and a dedicated instance. See the Privacy Policy on oroom.one for details.
More: oroom.one → Privacy Policy
Oroom One: pricing and implementation
You pay a subscription for scale, a one-off fee for the launch, and separately only for SMS and WhatsApp. Every plan includes all platform features, and contacts and emails are unlimited (to your own database with consents).
• Choose the plan by the higher of two thresholds: the number of products in your catalog or the size of your team. The plans are Start, Growth, Pro and Enterprise, from PLN 299 net per month.
• Implementation is a one-off fee depending on the scope: Standard (launching the instance and connecting your store or product source), Onboarding PRO (training on top) or Onboarding Enterprise (integrations and changes for your process, after a pre-implementation analysis).
• You can also buy support (hours of the Oroom team per month) and SMS packages; WhatsApp is billed at Meta rates.
Current prices, plan limits and implementation scopes are on the Pricing page. If you are not sure which plan to choose, book a short presentation and we will match it to your catalog and team.
More: oroom.one/en/pricing
No. The best results come from starting with one process that limits your sales most today and adding modules in stages. Examples of a first step:
• product offers for salespeople – an offer from the catalog under a link, tracking when the customer opened it, and a call at the right moment,
• order in leads – forms, consents, owners and an automatic welcome email,
• communication automation – reminders, follow-ups and tasks for the team.
You can also start with a pilot: a selected group of salespeople and one sales process. The pilot results help plan the next stages. All features are available in every plan, so expanding does not require a new tool or paying for modules – you change the plan only when your catalog or team grows.
Oroom One is one environment for sales, communication, content and customer service. In one panel you get:
• CRM – leads, organizations, deals, funnels, tasks and notes,
• product offers – personalized offers under a link with customer activity tracking, negotiations and payment,
• communication – email, SMS, WhatsApp and a shared Omnichannel inbox,
• automation (workflows), forms, surveys and GDPR consents,
• a headless CMS – pages, blog, FAQ, translations, multiple markets and languages,
• e-commerce and bookings, integrations, reports, AI and an MCP server.
Oroom works well in e-commerce and B2B (offers, quotes, negotiations), education and events (registrations, certificates, webinars) and real estate (inquiries, bookings, communication). You do not have to implement everything at once – start with the process that limits your sales most today.
Every implementation starts with a working instance connected to your store, payments and invoices. Depending on the package it includes:
• launching the instance (domain, SSL, users, panel branding),
• connecting your store or product source (platform, XML file, API),
• a sending domain (SPF, DKIM, DMARC), forms and GDPR consents,
• GA4, GTM and importing contacts from CSV,
• in higher packages – training, integrations beyond the ready list (ERP, warehouse), changes to fields, views and offer templates, and migration from another CRM.
Roughly: Standard up to 1 week, Onboarding PRO 1–2 weeks, Onboarding Enterprise 3–8 weeks after an analysis. After launch you get support (14 to 60 days depending on the package). The time to build a website on Oroom depends on the project size – the ready CMS, CRM and automation modules usually shorten it a lot.
More: oroom.one/en/pricing
The panel has a consistent layout: every list (leads, deals, offers, products) has the same tools – search, filters, saved filters, table settings and actions. Once you learn one list, you can handle the others.
Support depends on the package:
• during implementation we go through the configuration and first processes with you, and in the PRO and Enterprise packages we run 1:1 or team training,
• after launch you have a support period (14 to 60 days),
• you can buy ongoing support – hours of the Oroom team for changes, new automations and consultations,
• you report problems in the panel: Help Center → New ticket.
Answers to typical “how do I” questions are in this Help Center, in categories that match the panel modules.
Yes. We migrate websites and stores from WordPress, WooCommerce and other systems to an implementation connected with the Oroom CMS, CRM and automations. We can also move contacts and data from another CRM or automation tool – the migration scope is agreed when we quote the implementation.
For a store you do not always have to replace it: Oroom can work next to your store platform (for example through the Shoper or Base integration or your own API) and add a layer of offers, CRM and communication without migrating the catalog.
You can also import contacts from a file yourself: Sales → Import (CSV or XLSX files). Before importing, check active automations with the “Lead created” trigger, because they can run for every imported contact.
More: oroom.one → WordPress / WooCommerce / website migration
Oroom One works wherever a company needs one system for marketing, sales and customer service. We have ready starter environments for several industries:
• e-commerce and retail – a new sales channel that connects salespeople with your store (offers from the catalog, negotiations, checkout),
• B2B – managing business partners, quotes and negotiations, ERP integration,
• education and events – registrations, participant communication, webinars, certificates and progress tracking,
• real estate – listings, online bookings, analysis of customer preferences and automated communication.
If your industry is not on the list, let's talk – we configure the environment to the way your company works (fields, funnels, offer templates, automations).
More: oroom.one → Solutions
Getting started and account settings
Open the address of your Oroom One panel (you receive it during implementation) and log in with your email and password. On the login screen you can also choose the panel language (Polski / English).
• If you have added a passkey, click “Log in with passkey” – you log in with your fingerprint, Face ID or a hardware key, without a password.
• With two-factor authentication (2FA) enabled, the system will also ask for a code.
• Forgot your password? Click “Forgot your password?”, enter your email and set a new password from the link in the message. If the email does not arrive, check your spam folder or ask your administrator to check the address on your account.
After logging in you land on the Dashboard. Secure your account in Settings → Account security (more in the “Security, consents and GDPR” category).
Where in the panel: Panel login screen
The left icon bar has 9 sections: Dashboard, Sales, Offer and content, Forms and surveys, Automation and communication, Ecommerce, Analytics, Configuration and Omnichannel. Clicking an icon opens the section submenu, for example Sales → Leads list, Organizations list, Deals, Sales funnels, Notes, Import.
Useful shortcuts:
• “Pin sidebar” keeps the submenu visible,
• the “+” button at the top of the bar opens the “Add” menu: New lead, New product offer, New offer, New deal, New product and New task – it works from anywhere in the panel,
• the breadcrumbs at the top show where you are and let you go one level up,
• the “Search…” field in the header, the notifications bell and the account menu (avatar) are always at hand,
• the list icon in the bottom-left corner opens “Your tasks”.
Where in the panel: Left sidebar
The Dashboard is your daily starting point. You will see:
• Product offer events – offer opens, contact requests, offers forwarded, with an event type filter and an All / Mine switch; “All offer events” leads to the full analytics,
• Assigned to you – open, overdue and due-today tasks,
• Unread omnichannel – the number of unread customer conversations and an “Open inbox” button,
• the latest leads, deals and orders.
Customize the layout in “Dashboard settings”, and the Dashboard / Calendar switch shows your calendar of meetings and tasks. A good habit: in the morning check offer events and overdue tasks – that is your list of people worth talking to today.
Where in the panel: Dashboard
Every list in the panel (leads, deals, offers, products, orders…) works the same way:
• Search – quick search by name, email and so on,
• Filters – narrow the list by any fields; save a set of filters in “Saved filters” and return to it with one click (you can share a saved filter with your team),
• Table settings – choose and order the visible columns,
• Refresh – loads the latest data,
• Select records + Actions – operations on many records at once; check the progress (status, number of processed and changed records) in the bulk operations history,
• Items per page – at the bottom of the list.
Exported files are in the Export history (account menu): collection, status, number of records and files to download. Files are available for a limited time, so download them right away.
Where in the panel: Any list → bar above the table
These are two different things:
• The panel interface language (Polish or English) is chosen on the login screen with the Polski / English switch. The choice is remembered in your browser.
• Content languages are the language versions of what you publish: offers, forms, pages, blog posts, FAQ and email templates. Add a new language in Configuration → Languages → “Add new language” (name, language code, status). From then on, content editors show a language switch and you can fill in translations.
Leads also store a “Contact language”. Use it in automations, for example so that a customer with English gets an email from the English template and a Polish customer from the Polish one.
Where in the panel: Login screen / Configuration → Languages
Manage users in Configuration → User accounts. The list shows the first and last name, email and account status.
• A new team member: click “Add account” and fill in the details. The number of people depends on your plan (Start, Growth, Pro, Enterprise).
• An employee is leaving: first choose “Reassign owner” – leads and other records they owned move to the person you choose. Then click “Deactivate account”. You can reactivate or delete a deactivated account later.
• Changing details: “Edit” next to the account.
Ask every user to enable two-factor authentication right away (Settings → Account security), because accounts have access to customer data.
Where in the panel: Configuration → User accounts
A content creator is the profile of a person shown externally – most often the salesperson in a product offer. The profile has a first and last name, email, phone and profile photo, and can be linked to a panel user account.
When you choose the “Salesperson” in a product offer, the customer sees the content creator's details in the Contact section. The offer has the face of a specific person, and contact details stay up to date in all offers – changing the phone in the profile does not require editing every offer.
Add content creators in Configuration → Content creators → “Add content creator”. Remember the difference: the Salesperson (content creator) is the person the customer sees, and the Owner is the user account responsible for the offer in the panel.
Where in the panel: Configuration → Content creators
Instance settings are in the Configuration section:
• Company profile – your company details. If the section is not available to you, contact your administrator or the Oroom team.
• Lead settings → Lead collection rules – the “Contact identifier” (for example email or phone) the system uses to recognize that a lead already exists.
• Dictionaries: Categories (separate trees for products, the blog and offers, with subcategories), Brands (with logo), Regions and Tags. Dictionaries feed filters, forms and website content.
• Languages, Files, Integrations, User accounts and Content creators.
• Settings → AI, MCP connections and Account security.
Some settings (for example custom fields and field groups in the lead form, specific views) are configured during implementation – if you need something, tell the Oroom team.
Where in the panel: Configuration
All files uploaded to the panel are in Configuration → Files. The list shows the name, category (images, files, certificates), format, size with variants, date added, where it is used and access level. Switches at the top narrow the view to images, files or certificates, and “Details” shows information about the selected file.
The “Usage” column tells you where the file is used (for example in an offer, blog post or gallery) – check it before deleting a file so it does not disappear from published content.
You add images for products, galleries, offers and posts directly in their forms (“Add new image”) – they then go to the file library automatically. Generated participant certificates are also visible on the lead card (Sales → Certificates).
Where in the panel: Configuration → Files
In the panel open the Help Center and click “New ticket”. Describe the problem as specifically as you can:
• what you wanted to do and where in the panel (the breadcrumb path at the top of the screen),
• what happened – the error message, a screenshot,
• when it happened and whether it repeats.
The ticket list shows the number, subject, status, priority and creation date, and the Active / Closed switch takes you to the history. Use the ticket number in further correspondence – we will find the case faster.
If you have a support plan, you can also request changes and new automations in a ticket. Urgent business matters (pricing, implementation) are also handled at info@oroom.one.
Where in the panel: Help Center → New ticket
Leads and organizations
A lead is the profile of a customer or prospect: contact details, preferred channel (email, phone, WhatsApp), contact language, owner, organization, tags, address and consents. Deals, product offers, orders, bookings, surveys, certificates, notes and all communication are linked to the lead.
The lead card (Sales → Leads list → click a person):
• left column – contact details, consent icons, owner, quick actions: Add deal, Create product offer, Omnichannel, Create task; below that tasks, recent orders and deals,
• Profile – Data (lead form), Consents (with dates), Notes, Surveys,
• Communication – Messages, Emails, SMS, Calls,
• Sales – Deals, Offers (product offers), Orders, Bookings, Certificates.
Above the leads list you also see statistics for the selected period: the number of leads and deals, conversion, leads with email consent and the number of customer accounts.
Where in the panel: Sales → Leads list → [lead]
Click “+” → New lead or go to Sales → Leads list → “Add lead”. The form has sections:
• Basic information – first name, last name, email, phone (with country code), preferred communication channel, gender, plus source information (page and form location, form name),
• Details – contact language, owner, organization, company name, job title, tax ID,
• Tags and Address.
Click “Save”. Important: adding a lead is the “Lead created” automation trigger. If you have active scenarios (for example a welcome email or WhatsApp), they can immediately send a message to the new contact – use your own address when testing. Avoid duplicates with the “Contact identifier” setting in lead settings.
Where in the panel: Sales → Leads list → Add lead
Open the Import center (Sales → Import, or the “Import center” button above the leads list):
1) choose the data type: Leads, Organizations or Products,
2) select a CSV or XLSX file,
3) click “Upload file” and map the file columns to Oroom fields,
4) check the progress and result in “Your import history”.
Before importing leads:
• set the “Contact identifier” (Configuration → Lead settings) so existing contacts are recognized, not duplicated,
• check active automations with the “Lead created” trigger – they can run for every imported contact and send messages,
• make sure you have a legal basis for contact – import marketing consents only if you really have them.
Where in the panel: Sales → Import
Whether a new submission goes to an existing lead is decided by the “Contact identifier” setting (Configuration → Lead settings → Lead collection rules), for example “Email or phone”. When a form or import brings a contact with the same identifier, the system matches it to the existing lead instead of creating a new one.
If a duplicate already exists:
• compare both records – a lead is the center of data, so deals, offers, orders and communication history may be linked to it,
• move the information you need (for example notes, tags) to the record you keep,
• delete the unnecessary lead from the list (select the record → Actions).
If you want to combine two leads together with their history or delete data on a GDPR request, contact the Oroom team through the Help Center.
Where in the panel: Configuration → Lead settings
The owner is the team member responsible for the contact. Assign them:
• on the leads list in the “Owner” column – “Add owner” and choose an account; the cross next to the name (“End ownership”) removes the owner,
• in the lead form (Details section),
• automatically – with the workflow action “Update data” (for example every lead from the B2B form goes to a chosen salesperson).
Tabs above the list:
• Mine – leads you own (you also find them in the account menu → “Handled leads”),
• Unassigned – leads without an owner; review them daily so no inquiry is left unanswered,
• All – the whole database.
The same split works on the deals, product offers and tasks lists, and the owner is also the default assignee of tasks created by automations.
Where in the panel: Sales → Leads list → Owner column
Tags are labels that describe leads (for example “March webinar”, “B2B”, “VIP”). Add them in the lead form (Tags section); the tag dictionary with the number of leads and offers per tag is in Configuration → Tags.
A segment is a saved set of filters: set filters on the leads list (for example tag + contact language + email consent) and save them in “Saved filters”. You can share a segment with your team, and in survey analytics you can compare answers of different segments.
Tags also work in automations:
• adding and removing a tag are workflow triggers (for example the tag “Downloaded e-book” starts an email series),
• the “Add tag to lead” action marks customers at further stages of a scenario.
Remember that adding a tag manually can start an active scenario and send a message.
Where in the panel: Configuration → Tags / Leads list → Filters
Organizations are the companies you work with – especially useful in B2B sales, where several people from one company are involved. The list is in Sales → Organizations list. The organization card contains: name, email, phone, address (city, postal code, region, country), tax ID, REGON, KRS, domain, number of employees, source, company size by revenue and industry.
Links:
• assign a lead to an organization in the lead form (Details → Organization) – the leads list then shows a column with the company name,
• assign a deal to an organization in the “Organization” field – sales reports will show the value of opportunities per company,
• tasks can also be linked to organizations.
Import organizations from a CSV/XLSX file in the Import center (data type: Organizations).
Where in the panel: Sales → Organizations list
A lead is a record in your CRM, and a customer account is the customer's login to the portal (for example to view offers, orders or bookings, if your implementation has a customer portal). The account has its own email with verification, billing details and can be linked to a lead.
Worth knowing:
• the lead type (customer, unconfirmed customer, content creator) is visible in the lead data,
• creating a customer account and the customer confirming their email are separate automation triggers – for example you can send a welcome email only after the address is verified,
• the statistics above the leads list show the number of customer accounts in the selected period.
Whether customers create portal accounts in your instance depends on the implementation – if in doubt, ask the Oroom team.
Where in the panel: [lead] → Profile → Data
Sales: deals, tasks and notes
A deal is a sales opportunity – a specific case you handle with a customer. It connects a lead, an offer from the catalog, an organization, an owner, a net value and currency, and a place in the funnel (funnel and stage). It also has a type, for example general, webinar, on-site training, video, sample.
How to add one:
• “+” → New deal,
• “Add deal” on the lead card (the lead is filled in automatically),
• Sales → Deals.
Fill in the name, lead, offer, net value, organization and owner, choose the funnel and stage and click “Save”. A deal can also be created automatically, for example from a form submission attached to an offer – it then lands right away in the initial funnel and stage set in the offer.
Note: creating a deal is the “Deal created” trigger, which can start active automations.
Where in the panel: Sales → Deals
Change the stage in two ways:
• on the deals list in the “Sales funnel stage” column – choose the new stage from the dropdown,
• in the deal form.
Every change goes to the deal's “Funnel history” tab, so you see when and how the case moved through the stages. Add notes to the deal in the “Notes” tab.
A stage change is the “Deal stage changed” trigger. Use it for example to:
• create a “Prepare the contract” task when the deal enters the Contract stage,
• send a thank-you email after the “Down payment/Payment” stage,
• add a tag to the customer.
Deals from a catalog offer start in the “Initial funnel” and “Initial stage” set in that offer, so new inquiries land in the right place right away.
Where in the panel: Sales → Deals → [deal] → Funnel history
Configure funnels in Sales → Sales funnels. There are two kinds, in separate tabs:
• deal funnels (Deals),
• product offer funnels.
You can have several funnels, for example “Marketing” and “Sales” or a separate funnel for each product line. In each funnel:
• “Add stage” – add a stage (for example New contact, Diagnosis, Offer sent, Negotiations, Contract, Down payment/Payment, Handed over for delivery, Offer rejected),
• “Edit” and “Delete” – rename, reorder and delete stages.
Good practice: stage names describe a fact, not an intention (for example “Offer sent”, not “Send offer”), a separate stage for lost cases lets you analyze rejection reasons, and fewer stages (5–8) make it easier for the team to keep them up to date. Use stages in automations and in Funnel analytics.
Where in the panel: Sales → Sales funnels
Analytics → Funnel analytics shows:
• a report by funnel stage – number of deals, share, total value, forecast and forecast weight,
• a report by categories and templates – which offers and offer groups sell best.
Switch the report between Deals and Product offers and filter by currency and date.
What the data gives you:
• you see at which stage cases get stuck most often – that is where to add a task, a reminder or better material,
• the history of deals and offers on the lead shows what the customer was interested in before – it is easier to tailor the next proposal and communication,
• the forecast (value × stage weight) helps plan revenue and team capacity.
Data about customer activity in product offers is in Product offer analytics.
Where in the panel: Analytics → Funnel analytics
Notes are the team's internal memory – the customer does not see them, and each one stores the author and date. Add them to:
• a lead – lead card → Profile → Notes: type the content, optionally set a date and click “Add note”,
• a deal – “Notes” tab,
• a catalog offer,
• a product offer – Notes section in the offer summary.
A note added in a product offer is linked to the buyer, so it also appears on the lead card – the salesperson sees the full context without searching through offers. On the leads and offers lists, the “Notes” column shows the number of notes on a record.
Notes are not an automation trigger, so adding one never sends anything. A good note contains what was agreed and the next step, for example “Customer is comparing the Standard and Pro packages – call back on Thursday after 2 pm”.
Where in the panel: [lead] → Profile → Notes
All notes in one place are in Sales → Notes (“All notes”). The list collects notes from leads, deals and offers, with the author, date and the record they belong to. The All / Lead / Deal / Offer filters narrow the view, and counters at the top show how many notes each group has. The link next to a note leads to the record.
Delete a note with the trash icon – in this list or on the record card. Deletion is permanent and cannot be undone, so delete only notes that are really unnecessary (for example test or duplicate notes).
Tip: reviewing “All notes” from recent days is a quick way for a sales manager to see what is happening with customers without opening every card.
Where in the panel: Sales → Notes
Create a task with “+” → New task, the “New task” button in Dashboard → Tasks or “Create task” on a lead or product offer card. You set:
• title and description,
• type – call, meeting, email, project, offer, other,
• priority – low, medium, high,
• due date and the person responsible,
• links to leads, offers, product offers, deals and organizations.
The task list (Dashboard → Tasks) has status filters: All, Completed, In progress, Overdue, Pending, Pending today and tomorrow, the All / Mine / Unassigned split and a List / Calendar view. Open your own tasks with the icon in the bottom-left corner too.
Tasks can be created automatically – the workflow action “Create task” (type, priority, due date for example in 24 hours, assignment to the lead owner).
Where in the panel: Dashboard → Tasks
The calendar (Dashboard → Calendar or the Dashboard / Calendar switch) combines in one view:
• Oroom meetings – for example booked by customers from an offer,
• Oroom tasks with due dates,
• events from Google and Outlook calendars.
Views: Month, Week, Day and List. Previous / Today / Next switch the period, and “Sync and refresh” fetches the latest events from external calendars. The legend shows which source an event comes from.
To see your Google or Outlook calendar, connect the account in Configuration → Integrations → Google or Microsoft → “Accounts” tab (log in with the provider). The same connection can also be used for mail.
Where in the panel: Dashboard → Calendar
A customer can book a time in the salesperson's calendar, for example from a product offer – if the offer template has the salesperson's calendar assigned. No more agreeing on times by email.
Booked meetings are in the account menu → Meeting calendar: lead, date, note, contact, status and actions. They also appear in the Calendar as “OO meetings”. The account menu also has an “Availability” tab where you define when customers can book meetings.
Communication around meetings is handled by email templates, for example “Meeting reschedule proposal” and “Meeting cancellation”, and the email editor has “Calendars” and “Open calendar button” blocks. The details of meeting booking in your instance are configured during implementation.
Where in the panel: Account menu → Meeting calendar
Product offers
A product offer is a personalized proposal for a specific customer, published under a link as a page – instead of a PDF attachment. It contains products from the catalog with quantities, individual prices and discounts, a validity date and sections: description, video, gallery, FAQ, attachments, salesperson contact and decision buttons. After sending, you see what the customer does with the offer, you can negotiate terms and lead to acceptance and payment.
There are three roles in an offer:
• Buyer – the lead the offer is for,
• Salesperson – the person shown to the customer as the contact (a content creator profile),
• Owner – the panel account responsible for the offer.
A catalog offer (Offer and content → Offers list) is something else: an item in your company's offering, for example a service, training or webinar, with a registration form, certificate and initial funnel. Deals are created from it, while a product offer is a document for one customer.
Where in the panel: Offer and content → Product offers
Oroom records the customer's actions on the offer and shows them in several places:
• in the offer – the “Customer activity” section: number of visits, total time on the page, maximum scroll, last visit and language, button clicks (CTA), video viewing (time, percentage, watched to the end) and the engagement level, for example “High”,
• in the offer – “Product offer history”: a timeline of events from creation through sending to the customer's decisions,
• on the Dashboard – “Product offer events” from all offers: offer opened, file downloaded, offer forwarded to another person (with the recipient's address), CTA click, video watched, contact request, negotiations.
How to use it: several visits, scrolling to the end or forwarding the offer is a good moment for a call. Remember, though, that activity alone does not decide the purchase – treat it as a hint for the conversation.
Where in the panel: [product offer] → Customer activity / Dashboard → Product offer events
1) Click “+” → New product offer or “Create product offer” on the lead card (the buyer is filled in automatically).
2) Click “Choose a product offer template” – the template adds default products, sections, FAQ, gallery and settings.
3) Basic information: Salesperson, Buyer, Offer expiry date, Owner, Funnel and Funnel stage, Title (automatic or manual) and UI variant – Classic or Compact (a dense document layout with an items table, summary and the decision button always at hand).
4) Products: “Add product” or “Add several products”, quantities, prices, discounts; group items into sections (for example stages, rooms, zones).
5) Offer sections: turn sections on or off and arrange their order.
6) Advanced: currency and additional items.
7) Click “Save” and check the “Product offer preview” – you see exactly what the customer sees.
Send the finished offer with “Send to customer”. Creating an offer is an automation trigger, so use your own address as the buyer when testing.
Where in the panel: + → New product offer
A template stores everything that repeats in your offers, so you prepare a new offer in a few minutes. In a template you set:
• default products and how they are presented (cards or a table, column names),
• the order, names and visibility of sections: Intro and description, Video, Products, Price summary, Customer actions, Additional information, Additional list, Negotiations, Contact, Gallery, FAQ, Attachments,
• FAQ – questions from a category, selected questions or a custom list,
• a gallery, a custom list (for example “What the price includes”) and video (uploaded or from a link, with viewing analytics),
• a form, a survey shown when the offer is rejected and the salesperson's calendar for booking meetings,
• available customer actions and messages shown depending on the customer's behavior (engagement messages),
• the funnel and stage a new offer goes to.
Templates are in Offer and content → Product offer templates. Instance-wide product offer settings are in Configuration → Product offer.
Where in the panel: Offer and content → Product offer templates
In the Products tab each item can have its own price, quantity and percentage discount, and the whole offer an additional amount or percentage discount. The net value and currency are visible in the offer summary, and the customer sees a clear price summary in the “Price summary” section. The salesperson can close the terms on the spot, without sending a new file.
Catalog price vs. offer: when an offer is published, its commercial terms are locked – prices, discounts and also SKUs and taxes. A later price change in the catalog does not change the offer the customer already received. No more “but we agreed otherwise” disputes.
If you want to update the terms for the customer, edit the offer (or prepare a new version with “Clone product offer”) and send it again. An offer can go through: preliminary proposal → negotiations → final offer → acceptance → payment.
Where in the panel: [product offer] → Edit → Products
In the offer summary click “Send to customer”. You can share the offer:
• as a link (copy it from “Product offer information” → “Link for the customer”),
• by email – from the “Product offer handover” template,
• by SMS or WhatsApp.
The customer does not need an account – they open the offer in the browser under a dedicated link, on a computer or phone. The “Visible” tag shows whether the offer is publicly available.
After sending, the status changes to “Sent to customer”, and the “Product offer sent” event can start automations, for example a reminder after 2 days. Send an additional email about the offer from the “Customer” card in the summary (“Send email”) – it goes to the lead and offer history.
Where in the panel: [product offer] → Summary → Send to customer
An offer goes through statuses:
• Draft – the offer is being prepared,
• Preliminary proposal – a first version to discuss with the customer,
• Sent to customer – the customer received the link,
• Active – the offer is published and valid,
• Accepted – the customer accepted the offer,
• Accepted and paid – the customer accepted and paid,
• Rejected – the customer rejected the offer,
• Cancelled – the offer was withdrawn.
The status is shown in the offer summary and in the “Offer status” column on the list. Regardless of the status, the offer also has a stage in the product offer funnel (for example Offer sent, Negotiations, Down payment/Payment), which describes your sales process.
Every status change is the “Product offer status changed” trigger – for example after acceptance you can automatically send a thank-you message and create a task for the fulfilment team.
Where in the panel: Offer and content → Product offers
Analytics → Product offer analytics collects the status of all offers:
• the product offer performance funnel – how many offers went through each stage,
• “Product offers that need attention” lists: Hot (high engagement or CTA clicks without a purchase), Not opened (sent but not viewed), Expiring soon and Checkout problem (started or failed payment),
• offer stages and the most active offers,
• a table with all offers: salesperson, number of products, status, value, visits, scroll, time on page, CTA, engagement, checkout, suggested next action, last activity, and the creation, publication, sending and expiry dates.
Filter by creation date and salesperson. A good routine: every morning check the “Hot” and “Checkout problem” lists – these are the customers worth calling first.
Where in the panel: Analytics → Product offer analytics
Negotiations: if the Negotiations section is enabled in the offer, the customer can propose changes to the terms directly in the offer. The negotiation history is visible in the offer, and submitting, accepting and rejecting a negotiation are separate automation triggers – for example you can notify the salesperson with a task right away or send the customer a confirmation. Negotiations end when the offer is accepted, rejected, paid or cancelled.
Contact request: the customer can click a contact request button in the offer. Then:
• the “Customer requested contact” event appears on the Dashboard and in the offer history,
• the “Contact requested” trigger can send the customer a confirmation (the “Confirmation of contact request about an offer” template) and create a task for the salesperson.
Which buttons the customer sees is set in the offer template (available customer actions).
Where in the panel: [product offer] → Offer sections → Negotiations
The customer usually decides in the offer itself (accepts, rejects or pays). If the decision was made outside the portal – for example by phone, or the customer paid by bank transfer – record it manually:
• in the offer summary open the “Customer decisions” section,
• enter a “Decision note”: the source of confirmation (for example “customer's email of 12 Nov”) or the reason for rejection,
• use the matching button, for example “Confirm payment outside the system”.
The entry goes to the offer history, and the status change can start automations.
Rejection reason: in the offer template choose a survey shown on rejection (for example a “Rejection survey” with “why not?” questions). Answers go to the Surveys module, the lead card (Profile → Surveys) and Survey analytics – you will see whether you lose most often on price, timing or scope.
Where in the panel: [product offer] → Customer decisions
Yes – if the purchase path is enabled in your implementation. The customer accepts the offer and goes to payment (for example via Stripe or in your store), without the salesperson re-entering the order. We configure and test the path during implementation, including the correctness of prices and statuses.
You see the payment state in the offer and in analytics: checkout started, payment pending, payment failed, paid or abandoned. Offers with a payment problem go to the “Checkout problem” list in Product offer analytics – a good signal for quick contact.
After payment the status changes to “Accepted and paid”, and an order can be created from the offer. If the customer paid outside the system, record it with “Confirm payment outside the system” in the Customer decisions section.
Where in the panel: [product offer] → Summary
The expiry date defines how long the offer is valid for the customer. Set it when creating the offer and change it in the edit view: Basic information → Offer expiry date → Save. Offers that are about to expire are on the “Expiring soon” list in Product offer analytics.
Build reminders in automations (Automation and communication → Workflows), for example:
• “Product offer sent” → Wait 2 days → Condition: offer not opened → Send a reminder email,
• a reminder 48 hours before the offer expires,
• a task for the salesperson when the customer opened the offer several times but did not decide.
Scenario conditions can use customer activity data (for example whether the offer was reviewed), so the reminder goes only to the people who need it.
Where in the panel: [product offer] → Edit → Basic information
Product offers have their own funnels, independent of deal funnels. Configure them in Sales → Sales funnels → Product offers tab (for example stages: Offer sent, Offer read / Call about the offer, Negotiations, Contract, Down payment/Payment, Handed over for delivery, Offer rejected).
Change an offer's stage:
• on the product offers list in the “Funnel stage” column,
• in the offer summary in the “Funnel stage” field,
• automatically – set the starting funnel and stage in the offer template.
A stage change is the “Product offer stage changed” trigger, so you can for example create a “Prepare the contract” task or send an email with documents. See funnel results in Analytics → Funnel analytics (Product offers tab) and in Product offer analytics.
Where in the panel: Offer and content → Product offers → Funnel stage column
The product offer summary has buttons:
• PDF and XLSX – download the offer as a document or spreadsheet; you can also export item data to CSV with the discount split correctly, for example for accounting or the warehouse,
• “Clone product offer” – a copy of the offer where you change the buyer, products or prices; useful for similar inquiries and for a new version of the terms,
• “Create task” – a task linked to the offer (for example “Call after the weekend”),
• “Add note” in the Notes section – an internal note, also visible on the buyer's card.
If you often prepare similar offers, create a product offer template instead of cloning – changes in the template do not affect offers already sent.
Where in the panel: [product offer] → Summary
Customer communication
On the lead card in the Communication tab:
• Messages – conversations from the portal and Omnichannel (for example chat, WhatsApp replies),
• Emails – all emails sent to the lead: by users (for example from a product offer), by automations and by the system; with the template, status and date,
• SMS – sent text messages with content, date and success information,
• Calls – phone calls from Ringostat: direction, duration, recording and transcription summary.
Next to it, the Sales tab has offers, deals, orders and bookings, and the Profile has team notes and surveys. Before talking to a customer, you can check in seconds what was agreed and what they received. Open a live conversation with the “Omnichannel” button on the lead card.
Where in the panel: [lead] → Communication
Email goes through three layers: the mail account (sender), the template (content) and the sending context. The result always goes to the Message history and the customer card.
• Senders: the Oroom system account, your own accounts (SMTP) and Gmail and Outlook connected in Integrations.
• Content: email templates – transactional, marketing, notifications and system.
• Sending context: a product offer (“Send to customer”, “Send email”), email campaigns, automations (the “Send email” action), system emails (password reset, address verification, codes), order, booking and meeting emails.
• Data: the lead's email (sending address and – depending on settings – the identifier for recognizing duplicates), email marketing consent, organization, content creator and customer account email (with verification) and the webinar report email in an offer.
• Reactions: opening an email and clicking a link are automation triggers, and customer replies go to Omnichannel.
Mail accounts are in Automation and communication → Mail → Settings → Mail accounts:
• System accounts – a mailbox provided by Oroom, ready to send from day one,
• Custom accounts – your own mailboxes (“Add mail account”).
For each account you see its type (Oroom, other, Gmail, Outlook), display name, status (running, stopped, error, token expired) and the visibility of received emails: shared (the team sees the correspondence on customer cards) or private.
Connect Gmail or Outlook in Configuration → Integrations → Google or Microsoft → “Accounts” tab (log in with the provider) – the same connection also handles the calendar. An email template can have its own sender name and address.
For good deliverability you need a sending domain with SPF, DKIM and DMARC records – we configure it during implementation.
Where in the panel: Automation and communication → Mail → Settings → Mail accounts
“Token expired” usually appears when the password of the Google (Gmail) or Microsoft (Outlook) account was changed or the provider's authorization expired. “Error” means the mailbox cannot connect (for example changed SMTP details). Until the status returns to “Running”, emails from this mailbox are not sent – this also applies to automations and offers that use it.
What to do:
1) go to Configuration → Integrations → Google / Microsoft (or Mail → Settings → Mail accounts),
2) connect the account again (authorize access with the provider),
3) check that the status is back to “Running”,
4) in Mail → Message history see which messages were not sent and resend them if needed.
Accounts that need attention are marked on the integrations list – review it after every password change.
Where in the panel: Automation and communication → Mail → Settings → Mail accounts
Go to Automation and communication → Mail → Templates and add a template. In the template settings enter the name, type (transactional, marketing, notification, system), language, sender (name and address), subject and preheader.
Build the content in the drag & drop editor:
• Blocks: text, image, button, social buttons, divider, marketing opt-out button,
• data blocks: ordered products table, order details, invoice details, customer details, calendars and open calendar button, booking details, date and resource, booking payment, bookings table, add-on products, webinar summary, participant list, chat history,
• Layouts – ready column structures; Styles – colors and fonts,
• Variables – insert lead, offer or order data (also in the subject),
• “Generate with AI” – AI writes or improves the content.
The Mobile / Desktop preview shows how the email looks on a phone and a computer. Save the template – use it in automations, campaigns and offers.
Where in the panel: Automation and communication → Mail → Templates
Before using a template:
• check the Mobile and Desktop preview,
• click “Test message” – the system sends a real email to the address you enter; use your own address, not a customer's,
• check the variables (for example first name, offer number) – in a test they may be empty or sample values,
• “Download as PDF” is useful when someone else needs to approve the content.
System templates handle key messages: password reset, password reset token, email address verification and verification code (similar templates exist for SMS). You can change their look and content, for example add a logo and footer, but do not delete them – without them customers and users will not get login links or codes.
Tip: name templates so it is clear where they are used (for example “Product offer – reminder after 2 days”) and remove duplicates – it makes choosing a template in automations easier.
Where in the panel: Automation and communication → Mail → Templates → [template]
Automation and communication → Mail → Message history shows all sent emails: template, lead, address, status and date. Emails can be sent by users, automations or the system, and each email is linked to the right record – lead, deal, offer, product offer, order, booking or meeting. Sent emails have shared visibility (the team sees them on customer cards) or private.
See one customer's history on their card: Communication → Emails.
Use opens and clicks in automations – there are “Sent email — opened” and “Sent email — link clicked” triggers. Example: the customer clicked the pricing link → a task for the salesperson “Call today”.
If an email has an error status, check the recipient's address and the status of the mail account it was sent from.
Where in the panel: Automation and communication → Mail → Message history
Campaigns are in Automation and communication → Mail → Campaign history. A campaign combines an email template with a group of recipients and a time window (start and end date). It can be linked to a catalog offer, a product offer or a booking – for example a webinar invitation or news about a new offer.
Key settings and information:
• the “only with email consent” option – sending only to people with an active email marketing consent; always keep it on for marketing campaigns,
• statuses: scheduled, active, successful, error, cancelled,
• the number of emails sent and campaign statistics.
For marketing campaigns use “marketing” type templates with a marketing opt-out button. Sending based on customer behavior (for example a welcome series) is better built with automations. Emails to your own database with consents are unlimited (within fair use).
Where in the panel: Automation and communication → Mail → Campaign history
The SMS module is in Automation and communication → SMS:
• Message history – phone number, content, sending date and success information,
• SMS templates – title, type (verification code, password reset, phone change or other), sender and variables.
Send an SMS:
• in an automation – the “Send SMS” action (for example a reminder the day before a meeting or booking),
• as a sending channel for a product offer.
See a specific customer's SMS history on their card: Communication → SMS.
Remember the consent for SMS communication – for marketing send only to people who gave it (consents are visible on the lead card). SMS are billed separately in packages (current prices on the Pricing page). A short, specific message with one link works best.
Where in the panel: Automation and communication → SMS
The WhatsApp module (Automation and communication → WhatsApp) has three tabs:
• Message history – template, lead, number and status: queued, sending, sent, delivered, read, failed, received,
• Templates – approved WhatsApp templates with name, language and components (type: reminder or other),
• Settings – connection configuration.
Send messages from automations (for example after a tag is added or before a booking date) or as a sending channel for a product offer. Customer replies go to Omnichannel, where you can continue the conversation.
Important: WhatsApp requires approved templates for business-initiated messages and the customer's consent to communication through this channel (the consent is visible on the lead card). Messages are billed at Meta rates.
Where in the panel: Automation and communication → WhatsApp
Omnichannel is a shared inbox of customer conversations – the last icon on the sidebar. Messages from different channels arrive here (for example chat, WhatsApp, received emails from accounts connected to Omnichannel).
• Conversations are split into “Known” (linked to a lead) and “Unknown” (a sender not yet linked to any lead, for example a new website chat).
• The number of unread conversations is visible on the Dashboard (“Unread omnichannel”).
• Open a conversation with a specific customer with the “Omnichannel” button on their card.
• Once a conversation is linked to a lead, it moves to “Known” and its history appears on the lead card (Communication → Messages). If the sender is a new customer, add them as a lead with the same email address or phone number.
• Prepare quick replies as Omnichannel templates, and connect mail accounts to the inbox in Mail → Settings → Omnichannel tab.
A new message can start an automation (the “Omnichannel — new message” and “Message received from lead” triggers).
Where in the panel: Sidebar → Omnichannel
Automation
A workflow is a scenario that performs steps by itself after an event occurs. It consists of:
• a trigger – the event that starts it (for example “Lead created”, “Product offer sent”, “Deal stage changed”),
• conditions – who it should work for (for example only leads with Polish as the contact language),
• actions – what should happen (send an email, SMS or WhatsApp, wait, add a tag, create a task, update data), with Yes / No branches.
Most often companies automate:
• customer communication – welcoming a new lead, offer reminders, confirmations, follow-ups,
• handling inquiries and purchases – tasks for salespeople, assigning an owner, tagging, reactions to acceptance, payment or rejection of an offer,
• bookings and orders – confirmations, reminders, status changes.
Create scenarios in Automation and communication → Workflows and organize them in groups (for example “New lead”, “Product offer”). The list shows the state of each scenario and the result of its last run.
Where in the panel: Automation and communication → Workflows
There are 35 triggers in 12 groups (you choose them when creating a scenario, with search and a group filter):
• Leads and tags: lead created, tag added to lead, tag removed from lead
• Customer accounts: customer account created, customer email confirmed
• Deals and funnels: deal created, deal stage changed
• Product offers: created, sent, status changed, offer stage changed
• Offer activity: view, file download, forward, CTA click, video watched
• Negotiations: negotiation submitted, accepted, rejected
• Contact and messages: contact requested, message received from lead
• Messages: sent email — opened, sent email — link clicked, Omnichannel — new message
• Orders and payments: including order created
• Bookings: confirmation, cancellation, down payment paid, needs attention, status change
• Shipments: shipment status change
• Products: product status change
Custom events from your website or app can be added as part of the implementation.
Where in the panel: Workflows → New scenario → Choose a trigger
After the trigger you add action blocks (“Add free block” or “Add branch” next to a block):
• Send email – from a chosen template, with record data in variables,
• Send SMS and Send WhatsApp message,
• Add tag to lead,
• Create task – title, description, type (for example call, email), priority, due date (for example in 24 hours) and assignment, for example to the lead owner,
• Wait – a delay in minutes, hours or days,
• Condition – branching into Yes and No based on data (for example whether the offer was opened),
• Update data – changing a record field, for example setting the lead owner.
Depending on the implementation there are also: document generation (certificate, contract), sending invoice data, sending a survey and changing the funnel stage. You can name blocks, duplicate them (“Duplicate block”), disconnect and arrange them (“Arrange blocks”), and each block shows whether its settings need to be completed.
Where in the panel: Workflows → [scenario] → Add free block
After clicking the trigger, set in the “Block” panel:
• Run conditions – rules checked on the record's data at the moment of the event, for example Lead → Contact language = Polish. Any field of the record related to the trigger can be a filter (for a deal: deal, lead and offer data). Combine rules with AND / OR and group them (“Add group”).
• Event rules – details of the event itself, for example a stage change specifically to “Negotiations”.
• End when — current data – stops a running scenario when the data changes, for example the customer already replied or accepted the offer (so you do not send a reminder).
• Run rules – “Re-run for a record” (for example on every matching event or after a break) and “Allow parallel runs”.
Conditions are checked at the moment of the event, and in scenarios with a “Wait” block it is worth adding a “Condition” block before sending, to check the current data.
Where in the panel: Workflows → [scenario] → Block → Run conditions
1) Go to Automation and communication → Workflows and add a new scenario.
2) Choose a trigger, for example “Product offer sent”.
3) In the “Block” panel set the run conditions (for example only offers from a chosen funnel).
4) Add blocks: “Wait” (2 days) → “Condition” (offer not opened) → on the Yes branch “Send email” with a reminder template, on the No branch for example “Create task” for the salesperson.
5) Name the blocks and the scenario, use “Arrange blocks”.
6) Set the run rules (whether the same record can go through the scenario again).
7) Click “Save draft” – a draft does not run until you publish it.
8) Check the scenario on a test record (your own email address) and only then click “Publish”.
The scenario state (for example “Active · Published”) is shown under its name. Changes to a published scenario are saved as a draft – until you publish, the previous version keeps running, and “Load current version” brings it back into the editor.
Where in the panel: Automation and communication → Workflows
Proven scenarios to start with:
• Welcoming a new lead – “Lead created” → condition: contact language → “Send email” with the Polish or English welcome template → “Add tag”.
• Owner and task – “Lead created” from the B2B form → “Update data” (owner) → “Create task: call within 24 h”.
• Offer reminder – “Product offer sent” → wait 2 days → condition: not opened → reminder email; a second scenario – a reminder 48 h before expiry.
• Hot customer – “Product offer — CTA click” or “Contact requested” → a high-priority task for the salesperson.
• After the decision – “Product offer status changed” to accepted → thank-you message and a task for fulfilment; to rejected → an email with a survey.
• Deal stage – “Deal stage changed” to “Contract” → task “Prepare the contract” and a tag.
• Bookings – a confirmation and an SMS reminder the day before.
Test every scenario on your own address first.
Where in the panel: Automation and communication → Workflows
Open the scenario and click “Run history” – you see runs split into Success, Error, In progress and Skipped, with the time, triggering event, record (for example deal, lead) and result. On the Workflows list the “Last run” column shows the result of each scenario's last run.
• Success – the scenario performed its actions.
• Skipped – the trigger fired, but the record did not meet the run conditions (for example a different contact language) or was blocked by the run rules (for example the scenario cannot repeat for the same customer). It is not an error but correct filtering.
• Error – for example the lead has no email address, a template needs completing or there is a mail account problem.
Emails sent by automations are also in Mail → Message history (executor: automation) and on the lead card.
Where in the panel: Workflows → [scenario] → Run history
An active scenario runs on every matching event – also when you cause it manually. Sending can be triggered by, among others:
• adding a lead – manually, from a form and from an import (every imported contact!),
• adding or removing a tag,
• creating a deal and changing its stage,
• creating, sending, changing the status and stage of a product offer,
• an order, payment, shipment, booking, customer account.
Notes and tasks are not triggers – adding them sends nothing.
How to test safely:
• keep test scenarios in a separate group (for example “TESTS”),
• add a condition limiting them to a test tag or your own email address,
• publish only after checking the Run history,
• before an import or bulk changes, review the list of active scenarios (Status column) and temporarily turn them off if needed.
Where in the panel: Automation and communication → Workflows
Forms and surveys
Forms are in Forms and surveys → Forms. Click “Add form” and fill in:
• the name (visible only in the panel) and the title, short description and description visible to the customer,
• form fields (“Add item”), for example first name, email, phone, company, message,
• the consent group shown under the form.
You can prepare texts in several languages – the language switcher is at the top of the form.
When a customer submits the form, Oroom:
• creates a new lead or updates an existing one (recognized by the contact identifier set in Configuration → Lead settings),
• saves the form name and the place it was sent from,
• saves the accepted consents with the date,
• can start automations – for example “Lead created” with a welcome message and a task for the salesperson.
Where in the panel: Forms and surveys → Forms → Add form
You can use one form in several places:
1) Catalog offer – in Offer and content → Offers list choose the form in the “Form” field, for example a webinar or training registration.
2) Product offer – choose the form in the product offer template, for example to collect additional information from the customer.
3) Your website – the form connects to Oroom through the API, so it is embedded on the website by the implementation team or your developer. The page editor in the panel has no form block.
Assign the right consent group to each form. Its “Front-end ID” lets the website display the right consents, and Oroom saves them on the lead card.
Tip: use separate forms for different purposes (for example contact, training registration, B2B inquiry). The form name is saved in the lead's data, so in automations and segments you can easily tell the sources of inquiries apart.
Where in the panel: Forms and surveys → Forms
Submitting a form creates or updates a lead, so you build the automation on the “Lead created” trigger:
1) In Automation and communication → Workflows add a scenario with the “Lead created” trigger.
2) In the run conditions limit it to a specific source, for example the form name or contact language.
3) Add actions, for example:
• “Send email” with a welcome template or a registration confirmation,
• “Add tag to lead”, for example “webinar-november”,
• “Create task” for the salesperson: “Call back within 24 h”,
• “Update data”, for example set the lead owner.
4) Save the draft, test it on your own email address and publish.
Remember: send marketing messages only to people who accepted the right consent in the form. Transactional emails, such as a registration confirmation, are part of handling the request.
Where in the panel: Automation and communication → Workflows
Create surveys in Forms and surveys → Survey templates → new survey. Fill in the name, consent group, title and description (for example the purpose of the survey), then add question groups. You can prepare the content in several languages.
Where to use a survey:
• a satisfaction survey – after a call, meeting or completed delivery,
• a survey on offer rejection – attach it in the product offer template, and a customer who rejects the offer can say “why not?” right away,
• a needs assessment – before preparing an offer,
• in an automation – if sending surveys was configured in your implementation (for example a day after a visit).
Completed surveys go to the Surveys tab with a status (new, submitted, approved, rejected) and to the customer card: Profile → Surveys. A short survey (3–5 questions) usually gets far more answers than a long one.
Where in the panel: Forms and surveys → Survey templates
You can check the results on three levels:
• All answers to a survey – Analytics → Survey analytics: choose the survey, optionally the offer it was about, and narrow the results with filters, including saved segments (for example only B2B customers). You can export the results for further analysis.
• A single answer – Forms and surveys → Surveys: open a survey to see the answer preview and a quick summary.
• A specific customer's surveys – on the lead card in Profile → Surveys.
How to use it: answers from the offer rejection survey show whether you lose on price, timing or scope – a hint for improving your offer templates. Review satisfaction survey answers monthly with your sales and customer service team.
Where in the panel: Analytics → Survey analytics
Website and content (CMS)
Oroom One has a built-in (headless) CMS, so you edit website and app content in the same panel where you run sales. From the panel you manage:
• pages – a drag & drop block editor with SEO settings,
• the blog – posts, categories, galleries and publication dates,
• FAQ – questions and categories, also used in products and product offers,
• photo galleries and custom lists,
• translations – all fixed website texts (menu, footer, forms, messages),
• offers, products, brands and categories,
• files and images (Configuration → Files).
You can keep content in many languages. A new product, blog post or footer change appears on the website without a developer, and website forms feed the CRM right away.
Where in the panel: Offer and content
Oroom works as a headless CMS and backend: content, offers, products and customer data are in the panel, and the website or app (front end) gets them through the API. The preferred front-end technology is Next.js – Oroom provides API documentation and prepares missing endpoints as part of the project. The front end can be built by the Oroom team, your team or a partner agency.
Several websites in one panel: yes. From one panel you manage content, offers and products published on different websites and apps, and leads from many websites go to one CRM. This is useful for separate brand or market websites, or campaign landing pages.
The time to build a website depends on the size and complexity of the project. A ready backend (CRM, CMS, automations) shortens the work, because the team builds only the visual layer. If you have a WordPress website or a WooCommerce store, ask about migration.
Go to Offer and content → Pages and open a page. The editor works with drag and drop:
• Blocks – text, image, button, video, divider, social buttons,
• Layouts – ready column structures,
• Styles – colors, fonts and spacing,
• Settings – title, slug (subpage address), meta title and meta description for search engines.
The Mobile / Desktop preview shows how the page looks on a phone and a computer. Choose the language version with the language switcher – each version is edited separately. Click “Save” after making changes.
Tips:
• keep the meta title to about 60 characters and the meta description to about 155 – you can also write the meta description with AI,
• do not change the slug of a published page unless necessary – old links will stop working,
• more complex page elements (for example forms, offer sections) are part of the front end and are changed by the implementation team.
Where in the panel: Offer and content → Pages
Go to Offer and content → Blog and add a new post. Fill in:
• the thumbnail, title and short description (teaser on the post list),
• the slug, meta title and meta description (SEO),
• blog categories (set up the category tree in Configuration → Categories),
• a photo gallery and slider, if the post needs them,
• the publication date.
Write the content in the block editor, the same as for pages – with a Mobile / Desktop preview and language versions. AI can help you improve the text, shorten it, change the tone, translate it or prepare titles and the meta description.
“Save” saves and publishes the changes, and “Unpublish” hides the post from the website without deleting it. On the post list the Status column shows which posts are published.
Where in the panel: Offer and content → Blog
Manage the FAQ in Offer and content → Faq:
• Questions – the question and answer text (in each language) and the categories the question belongs to,
• Categories – the category name and description; one question can belong to several categories.
Where the FAQ is displayed:
• on the website – for example in the Help Center or on subpages, depending on how your front end was built,
• in products – the “FAQ category” field shows questions from the chosen category on the product page,
• in product offers – an FAQ section with questions from a category, selected questions or a custom list in the template.
Tips: write answers in full sentences, without referring people “to a consultant”; keep separate categories for pre-purchase questions (for example delivery, payment) and post-purchase questions (for example service). AI in the editor can suggest FAQ questions based on a product or offer description.
Where in the panel: Offer and content → Faq
These are reusable content – you create them once and show them in many places.
Photo galleries (Offer and content → Photo galleries):
• name, location, description and date (for example a project, event or investment),
• photos that you can reorder,
• use: blog posts and the Gallery section in a product offer, for example photos of previous projects that help the customer decide.
Custom lists (Offer and content → Custom lists):
• bullet lists, for example “What the price includes”, “Scope of service”, “Delivery stages”, “Warranty”,
• use: the “Additional list” section in product offers and offer templates.
Changing a list or gallery updates every place where it is used, so keep there the content you repeat in many offers.
Where in the panel: Offer and content → Photo galleries / Custom lists
Fixed website texts – for example the menu, footer, buttons, contact form, cookie banner, error messages or the password reset page – are changed in Offer and content → Translations:
1) choose a text group from the list (for example footer, contactForm, cookieConsent),
2) edit the values in each language,
3) click “Publish” – only publishing sends the new version of the texts to the website.
You can also import changes from a .json file (“Import (.json)”), which is useful when translating the whole website into a new language or for changes prepared by a translator.
Important:
• saving values without publishing does not change the website,
• do not delete translation groups if you do not know where they are used – the website may show empty spaces,
• add a new content language in Configuration → Languages.
Where in the panel: Offer and content → Translations
Set up categories in Configuration → Categories. There are separate trees for:
• products – with categories and subcategories, and “smart categories” that group products automatically by rules,
• the blog – post categories,
• catalog offers – for example trainings, consultations, webinars.
Each category has a name, description and slug (website address) in each language.
Brands (Ecommerce → Brands) are a list of manufacturers or brands with a name and logo – assign them to products, and customers can filter your offer by them on the website.
Tips: plan the category tree before importing products, keep 2–3 levels of depth and do not change the slugs of categories visible on the website unless necessary. You can also use categories and brands in list filters, segments and automations.
Where in the panel: Configuration → Categories
Store, products and bookings
A catalog offer is an item in your company's offering, for example a service, consultation, training or webinar. Add it in Offer and content → Offers list → New offer (or “+” → New offer). Fill in:
• the offer type and title, visibility in the portal, tags,
• the initial funnel and stage – deals created from this offer go there,
• the thumbnail, description and short description,
• a certificate (for example for training participants), category and registration form.
Offer templates (groups) – Offer and content → Offer templates – store shared settings: type, tags, funnel, description, certificate, category and form. With “Choose an offer template” you fill in a new offer in seconds, and the template also groups similar offers, for example successive editions of the same training.
A customer's sign-up for the offer creates a deal in its funnel, and the form data goes to the lead.
Where in the panel: Offer and content → Offers list
1) Add an offer in Offer and content → Offers list and choose the right offer type.
2) In the General tab set the webinar start and end.
3) Enter the “Webinar report email” – reports after the event (for example from ClickMeeting) go to this address.
4) Attach a registration form with a consent group.
5) Choose the certificate the participant gets after the training.
6) Set the initial funnel and stage, so each registration is a deal you can manage (for example Registered → Attended → Bought another training).
Next: in automations add a registration confirmation, a reminder a day and an hour before the webinar, and a message after the event with the recording or an offer. With the ClickMeeting integration, trainings, attendance and chats sync with Oroom, and you will find the summary in Analytics → Completed trainings.
Where in the panel: Offer and content → Offers list → [offer] → General
Certificates (Offer and content → Certificates):
• create a certificate template in the block editor – text, image, divider – on your own background (for example with a logo and signature),
• use participant and training data in the text,
• assign the template to a catalog offer, and Oroom generates a certificate for the participant,
• generated certificates are on the lead card: Sales → Certificates, and the files in Configuration → Files.
Contracts (Contract templates):
• prepare a contract template, and the system generates a PDF from it with the customer's data,
• the document can be generated automatically in an automation scenario, for example after a deal stage changes to “Contract” or after an offer is accepted – if configured in your implementation.
This way certificates and contracts need no manual re-typing of data, and all documents are linked to the right customer.
Where in the panel: Offer and content → Certificates / Contract templates
Go to Ecommerce → Products → New product (or “+” → New product). First choose the type: Standard or Booking (a service for a date). Then fill in:
• Basic information – name, slug, product line code, status (draft, published, archived), visibility in the portal, meta title and description, descriptions, brand, categories, FAQ category, photos, matching accessories, review moderation, owner,
• Price – net or gross, VAT rate, currency,
• Default variant – SKU, EAN, stock, low stock warning threshold, weight.
After saving, the product has tabs: Information, Variants and stock, Prices, Reviews and Orders with this product. You can archive or delete it on the product card.
Speed things up: product templates (Ecommerce → Product templates) fill in default fields, and you can import a larger catalog from a file (Sales → Import) or sync it from Base or Shoper.
Where in the panel: Ecommerce → Products → New product
Reviews are in Ecommerce → Reviews. For each review you see the date, product and variant, order, verified purchase mark, author, rating, comment, status and block reason.
How it works:
• turn on moderation in the product settings (the “Moderation” field) – new reviews then wait for your decision before they appear on the website,
• you can approve a review or block it, giving a block reason (for example profanity, personal data, spam),
• the “verified purchase” mark shows that the review comes from a customer who bought the product.
You can also see a product's reviews in its Reviews tab, and the average rating is visible in the product data.
Tip: respond quickly to critical reviews too, and do not block them just because they are negative – honest reviews build trust in your store.
Where in the panel: Ecommerce → Reviews
Orders are in Ecommerce → Orders – statistics are shown above the list, and filters and saved filters help you separate, for example, orders to fulfil.
Order statuses: new, needs quote, in progress, completed, cancelled.
Order details include:
• items, delivery cost and invoice details,
• shipping details and buyer details,
• the payment and its status,
• sellers (in the marketplace model),
• a message for the order.
The “Change shipment status” button updates the shipment. Order creation, payment and shipment status change are automation triggers – you can send confirmations, shipping notifications and review requests. You can also see a customer's orders on their card (Sales → Orders), and invoice data can go to wFirma.
The “needs quote” status is useful for orders where the salesperson sets the price, for example for non-standard quantities.
Where in the panel: Ecommerce → Orders
Delivery and payments are set for a sales market: Ecommerce → Sales markets → [market] (for example Poland). In the market settings you define:
• basic data – name, code, status (active) and market currency,
• supported countries – a group of countries or selected countries,
• delivery in this market – delivery methods with a gross price, VAT rate and free delivery threshold, as well as in-store pickup; change their order with the arrows,
• payments in this market – for example paynow, bank transfer, Stripe.
Currencies (Ecommerce → Currencies) have a code, name, symbol, status and availability. Turn on a new currency first, then assign it to a market.
Several markets are useful when you sell in different countries or currencies – each market can have its own delivery and payment methods. We set up the technical configuration of payment gateways during implementation.
Where in the panel: Ecommerce → Sales markets
Discount codes: Ecommerce → Discount codes → “Add new discount code”. Enter the name (the code the customer types), description, start date, discount percentage and scope – the products the code applies to. You can send the code in an email campaign, by SMS or in an automation, for example as a thank-you after the first purchase.
Abandoned carts and unpaid orders: Ecommerce → Store settings → Checkout settings.
• Abandoned carts – turn on detection and set the idle time after which a cart is considered abandoned. This lets you remind the customer about an unfinished purchase.
• Expiring unpaid orders – turn on automatic expiry and set the payment deadline (from 15 to 10,080 minutes, which is up to 7 days). After this time an unpaid order expires, and reserved goods go back on sale.
Remember to save each section with its own button.
Where in the panel: Ecommerce → Discount codes / Store settings
The Ecommerce → Stripe module shows:
• the connection status with your Stripe account,
• platform payments,
• Stripe Connect Marketplace – if your portal has many sellers,
• lists of payment collections, held payouts and refunds.
In the marketplace model the “Stripe sellers” section shows seller accounts, their verification status and missing formal requirements (for example company details, bank account). Until a seller completes them, their payouts may be held.
Turn on Stripe payments for a sales market (Ecommerce → Sales markets → Payments in this market). We configure the Stripe account connection during implementation.
Stripe also handles payments from product offers – the customer accepts the offer and pays right away. Failed or abandoned offer payments are on the “Checkout problem” list in Product offer analytics.
Where in the panel: Ecommerce → Stripe
Bookings are in Ecommerce → Bookings. You can work in the List or Calendar view (with the “Show cancelled” option).
Filters help you decide what to handle first: Need action, To settle on site, Today, Upcoming.
Booking statuses: new, needs attention, confirmed, cancelled. “Needs attention” means the booking needs a decision, for example when dates conflict.
You can see a specific customer's bookings on their card (Sales → Bookings).
Automations: confirmation, cancellation, down payment paid, “needs attention” and booking status change are triggers. Example: after confirmation the customer gets an email with the details, date and resource (the “Booking details” block in the template), and an SMS reminder the day before. When a booking needs attention, the team gets a task.
Where in the panel: Ecommerce → Bookings
1) Add a product in Ecommerce → Products → New product and choose the “Booking” type instead of “Standard”.
2) Set the additional options of the time-based service:
• resources – for example rooms, stations, equipment, specialists,
• pricing rules – a different price for example on weekends, in the season or at selected hours,
• date blocks – for example holidays, maintenance breaks, public holidays,
• add-on products – paid extras for the booking (for example equipment rental).
3) Set global rules in Ecommerce → Booking settings:
• hold duration in minutes – how long a slot is reserved for a customer who has not finished booking yet,
• hourly slot length in minutes,
• default time zone,
• whether a date conflict can be overridden manually and whether to show a warning when doing so.
Before launching, make a test booking with your own details and check the emails and SMS sent by automations.
Where in the panel: Ecommerce → Products → New product (type: Booking) / Booking settings
Integrations and reports
Ready integrations are in Configuration → Integrations, grouped by type:
• Calendars and mail – Google (Gmail, Google Calendar) and Microsoft (Outlook, calendar),
• Marketing – GetResponse,
• Webinars – ClickMeeting,
• E-commerce – Base (BaseLinker) and Shoper,
• Accounting – wFirma,
• Telephony – Ringostat.
Each integration has Overview (connection status) and Settings tabs, and some also have Sync history, Invoices, Trainings, Calls, Import or Accounts.
Besides ready integrations, Oroom has an API and webhooks, payments (Stripe, paynow), events for GA4 and GTM, and an MCP server for AI assistants. Integrations outside the ready list (for example ERP, warehouse, custom systems) are delivered as part of an Enterprise implementation.
Reconnect an integration showing a warning (for example an expired connection) in its tab – and check errors of individual operations in Sync history.
Where in the panel: Configuration → Integrations
Go to Configuration → Integrations → Sync history (or the Sync history tab of a specific integration). Each operation has:
• the creation date, service (for example Base, GetResponse) and action (for example create, update),
• the collection it concerns (for example products, leads, orders),
• the status, the item to sync (record), and the HTTP status and service response.
The number of current sync tasks is also shown above the table.
How to look for problems:
• filter by status to see only errors,
• the service response usually explains the cause (for example a missing required field, an invalid token, a rate limit),
• after correcting the data or reconnecting the integration, check that subsequent operations succeed.
If the error repeats, report it via the Help Center and include the date and the service response.
Where in the panel: Configuration → Integrations → Sync history
Oroom works alongside your store – you do not need to change platforms.
• Base (BaseLinker) – syncs products, stock levels and orders.
• Shoper – a native connection: you import products, customers and orders.
• Other platforms – connection via API, an XML file (product feed) or GTM; we confirm the scope before implementation.
What you gain: store customers go to the CRM as leads with their order history, salespeople build product offers from the current catalog, and automations react to orders and payments. The customer can also accept a product offer and buy in your store without re-entering the order – we launch and test this path during implementation.
Connecting your store or product source is part of every implementation package. Check the connection status and errors in Configuration → Integrations → Base / Shoper and in Sync history.
Where in the panel: Configuration → Integrations → Base / Shoper
The integration with the wFirma accounting system sends invoice data from Oroom, so you do not need to re-type orders for accounting.
• When an invoice is created – we agree on the scope during implementation, for example after an order is paid or at a chosen automation step (the send invoice data action).
• Where the data comes from – the order and the customer's invoice details (company, tax ID, address) and the order items.
• Where to check it – Configuration → Integrations → wFirma: the Settings tab (connection) and Invoices (the list of sent documents and their status).
If an invoice was not created, check the status in the Invoices tab and in Sync history – the most common causes are missing invoice details in the order or an expired wFirma connection.
The CSV of product offer items (with the discount split out) is useful if your accounting uses a different system.
Where in the panel: Configuration → Integrations → wFirma
ClickMeeting (webinars and online training):
• syncs trainings and webinars with offers in Oroom,
• shows attendance and reports – in Configuration → Integrations → ClickMeeting → Trainings and in Analytics → Completed trainings (an overall summary and the list of trainings in a chosen month),
• lets you export all training chats,
• sends reports to the “Webinar report email” set in the offer.
GetResponse (email marketing):
• syncs leads from Oroom to GetResponse, for example if you send newsletters from that tool,
• the lead's data (integrations section) shows the GetResponse contact ID and whether it was deleted.
Both integrations have a Sync history tab. Remember that customer consents apply when syncing contacts to a marketing tool – send only people with an active consent to the newsletter.
Where in the panel: Configuration → Integrations → ClickMeeting / GetResponse
After you turn on the Ringostat integration (Configuration → Integrations → Ringostat), phone calls go to customer cards automatically. On the lead card in Communication → Calls you see:
• the date and phone number,
• the owner who handled the call,
• the direction (incoming, outgoing) and status (for example answered, missed),
• the duration and call recording,
• the transcription status and call summary.
Before the next contact you can check in seconds what was discussed, and the team does not need to note every call manually. Still, save agreements that require action as a note or task.
Calls are linked to leads by phone number, so keep numbers in the CRM in full format (with the country code).
Where in the panel: Configuration → Integrations → Ringostat / [lead] → Communication → Calls
The Analytics module includes:
• Product offer analytics – the performance funnel, offers that need attention (hot, not opened, expiring, checkout problem), the most active offers and a table of customer engagement,
• Funnel analytics – a report by funnel stage (number of deals, share, total value, forecast and forecast weight) and a report by offer categories and templates, separately for deals and product offers, with currency and date filters,
• Survey analytics – survey results with filters and export,
• Completed trainings – a summary of ClickMeeting webinars.
You will also find statistics above the lead and order lists, and on the Dashboard – tasks, offer events, unread messages and the calendar.
You can export list data to a file (finished files are in the export history), and funnel events (for example offer sent and opened, purchase) can be sent to GA4. You can also prepare your own summaries by asking an AI assistant connected via MCP.
Where in the panel: Analytics
AI and MCP
AI helps you write and improve texts in the panel's content fields, for example in the email template editor (“Generate with AI”). Available actions:
• Fix language errors, Simplify language, Change tone,
• Shorten text, Expand text, Summarize,
• Translate – for example to prepare an English version of an email or description,
• Generate variants and Title variants – several options to choose from, for example email subjects,
• SEO meta description, CTA (call to action) and FAQ – for example questions for a product or offer,
• Next steps – a suggestion of further actions,
• Custom instruction – a command in your own words, for example “make this more formal, for a B2B customer”.
Always check the result before saving – AI can get facts, prices or names wrong. The selected text is sent to an external AI provider via OpenRouter, so do not paste data you do not want to share into AI fields. The monthly number of uses of each action is visible in the AI settings.
Where in the panel: Text fields in editors, for example Mail → Templates → Generate with AI
AI settings are in Configuration → Settings → AI. In the Configuration section:
• AI enabled – turns AI on or off in the whole panel,
• Active model and Fallback model – models available via OpenRouter; the fallback model works when the main one is unavailable,
• limits: maximum characters per request, requests per user per hour and requests for the whole instance per day,
• provider policy, key status and credit usage.
The Local usage section shows the number of requests today and this month, and Actions – the usage counter of each action. Recent errors help you understand why AI did not respond (for example a limit was exceeded).
Prompts: you can prepare your own version of the instructions for AI actions (a system prompt and a user prompt with the {text} variable), save it as a draft, test it (“Test”) and only then activate it.
The panel saves only usage metadata – prompt and response content is not stored in logs.
Where in the panel: Configuration → Settings → AI
Company knowledge is a document where you describe your business, offering, audience and communication rules. Fill it in in Configuration → Settings → AI → Company knowledge (Markdown format, up to 20,000 characters) and save it with “Save company knowledge”.
Currently MCP connections use this knowledge – for example Claude or Codex connected to your panel can read it before writing a product description, blog post, FAQ or customer messages. Only connections granted the “Company knowledge” permission when connecting the app or in service access can read the document, and only when you turn on “Share via MCP”. The document's change history is not shared.
What to describe:
• what the company does and what makes the offering stand out,
• who the offering is for and what problems it solves,
• the tone of communication (for example informal, no jargon) and words to avoid,
• fixed facts: area of operation, lead times, warranties, contact.
Update the document after every major change to your offering.
Where in the panel: Configuration → Settings → AI → Company knowledge
MCP (Model Context Protocol) is a standard that lets you connect an AI assistant – for example Claude, Claude Code or Codex – with the data in your Oroom panel. Once connected, you can ask questions in plain language and have content prepared.
Examples:
• “Show product offers sent this week that the customer has not opened”,
• “How many deals are in the Negotiations stage and what is their total value?”,
• “Compare the number of new leads this month and last month”,
• “Prepare a draft blog post / email template / FAQ questions about our new service”.
The scope depends on the permissions granted to the connection: the assistant reads only the collections it has access to, in read or read-and-write mode, and the maximum scope is set by the instance configuration. Writing includes, among others, creating and editing offers, FAQ, translations, blog post drafts and marketing email templates.
Important limits: through MCP the assistant does not send emails or messages, does not publish offers and does not delete records. You publish a blog post yourself in the panel, and you can always check changes in the MCP operation history.
Where in the panel: Configuration → Settings → MCP connections
Go to Configuration → Settings → MCP connections. The “Connection via user account” section has your panel's MCP address and ready commands.
• Claude (web and desktop): Customize → Connectors → Add custom connector. Paste the MCP address, leave the Client ID and Secret fields empty and log in to the panel.
• Claude Code: copy the commands with “Copy commands” (claude mcp add… and claude mcp login…) and run them in the terminal.
• Codex: the same way – the codex mcp add… and codex mcp login… commands.
When logging in you approve access to selected collections. The connected app appears on the “Apps connected via user account” list and renews access independently of your panel session.
The “Check connection” button tests whether the address is reachable from your browser and the login metadata – check the full login in the client itself. A cloud-based client (for example Claude in the browser) requires a public HTTPS address. If login fails, start the connection again in the client or report the problem via the Help Center.
Where in the panel: Configuration → Settings → MCP connections
Service access (Configuration → Settings → MCP connections → Service access) is for your own servers and background processes, for example a company integration. Enter the service name and click “Create access” – the service logs in with a client ID and secret, without a user session, and uses only selected collections in read or read-and-write mode. The table shows the client ID, status, creation date, last successful operation and permissions.
MCP operation history (Configuration → Settings → MCP operation history) shows operations from the last 90 days: account, app, operation name (for example offers_list, deals_list), changed fields, result and time. “Show errors” narrows the list to failed operations. Offer content and login data are not stored in the history.
Revoking access: revoke any access – an app connected via a user account or service access – on the MCP connections page. Revoking also blocks tokens already issued. Logging out other devices in Account security does not revoke MCP app access – you do that separately.
Where in the panel: Configuration → Settings → MCP connections / MCP operation history
Security, consents and GDPR
Oroom One has tools that help you protect data and communicate in line with the GDPR:
• Consents – you define consents (for example data processing, email marketing, SMS, WhatsApp, terms of service), collect them in forms and surveys, and see the status of each consent with acceptance and withdrawal dates on the customer card.
• Sending only where allowed – campaigns have an option to send only to people with consent, marketing templates have an opt-out button, and automations can check consents in their conditions.
• Secure login – two-factor verification (2FA), passkeys and control of active sessions.
• Access control – user accounts with deactivation, mailbox visibility (shared or private), permissions and an operation history for MCP connections.
• AI – the panel saves only AI usage metadata, without prompt or response content.
Data processing terms are set out in the agreement, and the Enterprise plan offers an individual data processing agreement and a dedicated instance. See the Privacy Policy on oroom.one for details.
More: oroom.one → Privacy Policy
Go to Configuration → Settings → Account security.
Two-factor verification (2FA):
• click “Enable 2FA” and confirm with your current password,
• scan the code in an authenticator app (for example Google Authenticator, Microsoft Authenticator),
• from now on, after entering your password you confirm the login with a code from the app.
Resetting the password by email does not turn off 2FA – even someone who takes over your mailbox cannot log in without the code.
Passkeys:
• enter a key name (for example “Work laptop”) and click “Add passkey”,
• confirm with biometrics (fingerprint, Face ID) or the device PIN,
• the passkey replaces the password and the 2FA code – you log in with one confirmation on the device.
Changing login methods requires a session created within the last 10 minutes – if the panel asks for it, log out and log in again. We recommend 2FA or passkeys for every account with access to customer data.
Where in the panel: Configuration → Settings → Account security
In Configuration → Settings → Account security → Active sessions you see all devices where you are logged in: system and browser, IP address, login date and last activity (updated every minute). The current session is marked “This session”.
• “Log out” next to a session ends it on that device.
• “Log out other devices” ends all sessions except the current one.
After losing a laptop or phone, or if it is stolen:
1) log in from another device and click “Log out other devices”,
2) change your password and turn on 2FA if it was off,
3) remove the passkey saved on the lost device,
4) in MCP connections revoke access of AI apps connected on that device – logging out sessions does not cover them.
If the device belonged to an employee who is leaving, the administrator deactivates their account in Configuration → User accounts.
Where in the panel: Configuration → Settings → Account security → Active sessions
You manage access and data visibility on several levels:
• User accounts (Configuration → User accounts) – add team members and deactivate the accounts of people who leave. Before deactivating, hand their customers, deals and tasks over to another owner.
• Record owner – leads, deals, product offers and tasks have an assigned owner. The All / Mine / Unassigned tabs let everyone work on their part of the database.
• Mail – mailboxes and sent emails have shared visibility (the team sees the correspondence on customer cards) or private.
• Integrations and AI – MCP connections have their own permissions to selected collections, and their operations are visible in the MCP operation history.
If you want to limit some people's access to whole modules (for example sales only, without settings and e-commerce), agree on it with the Oroom team during implementation or report it via the Help Center. The rule: everyone has access only to what they need for their work.
Where in the panel: Configuration → User accounts
Consents (Automation and communication → Consents and statements → “Add consent”) have:
• a name and content visible to the customer,
• types, that is what the consent covers, for example marketing emails, system emails, marketing and system SMS, marketing WhatsApp messages, data storage, data sharing, other,
• a mark whether the consent is required.
Examples: consent to data processing, consent to email, SMS and WhatsApp marketing, acceptance of the terms of service, consent to sharing data with a partner.
Consent groups (Automation and communication → Consent groups) are sets of consents displayed together, for example under the main contact form, in the meeting calendar or on a partner page. A group has a name, description and “Front-end ID” (for example MAIN_FORM), which the website uses to know which consents to show. Assign the group to a form or survey.
Agree on the wording of consents with a lawyer or data protection officer, and keep each marketing consent for a different channel separate.
Where in the panel: Automation and communication → Consents and statements / Consent groups
Quick view: on the leads list the “Consents” column shows an icon for each defined consent – green means accepted, gray means no consent or withdrawn.
Details: on the lead card in Profile → Consents you see the list of consents with their status and acceptance and withdrawal dates. This is your proof of when and to what the customer agreed.
Withdrawing consent:
• the customer can opt out of marketing with the opt-out button in a marketing email – that is why every marketing template should have one,
• after withdrawal the consent changes status, and the withdrawal date is saved,
• campaigns with the “only with email consent” option skip this person automatically.
Also remember automations: in scenarios with marketing messages add a condition checking the consent or a “Condition” block before sending. Transactional emails (for example an order or booking confirmation) are sent as part of providing the service, but do not put advertising content in them.
Where in the panel: Sales → Leads list → Consents column / [lead] → Profile → Consents
You usually have one month to respond to a customer's request. How to handle it in Oroom:
Providing data (right of access):
• open the lead card – the Profile, Sales and Communication tabs contain contact details, consents, deals, offers, orders, bookings, surveys, notes and message history,
• export list data to a file (filter for this customer → export); finished files are in the export history.
Deleting data (right to be forgotten):
• first check whether you must keep some data for other reasons, for example invoices and orders for accounting purposes,
• delete the lead from the leads list: select the record → Actions. The lead is the center of the data, so deleting it affects related deals, product offers, orders and communication history,
• if the data is also in integrated systems (for example GetResponse, your store), delete it there too,
• if in doubt, or when data linked in many places needs to be removed, report it via the Help Center.
Record when and how the request was handled – it is your proof in case of an audit.
Where in the panel: Sales → Leads list → Actions / Help Center
Promotions and partner program
It is a promotion for 100 companies that want to try consultative selling with product offers before the season. As part of the promotion:
• you get the Growth plan and the OO4Ecom Standard implementation for 0 PLN for 2 months from activation,
• the package includes OO4Ecom configuration and a product offer template, integration with your store (Shoper or via API/feed), import of your catalog, contacts and consents, GA4 and GTM setup, and onboarding: group sessions and a 1:1 call (60 min),
• you do not provide a card and there are no automatic charges – after 2 months you decide on a plan yourself; if you choose a plan before the 0 PLN period ends, you get a −30% discount for 12 months.
Only these are paid from day one: SMS and WhatsApp sending (per the price list), dedicated integrations (for example ERP, custom API) and custom work, always quoted before it starts.
Who can apply: companies with a Polish tax ID (NIP) running an online store or B2B sales where some orders are created by a salesperson. One place per tax ID. Sign-ups are open until 30.11.2026, 23:59, or until places run out. We reply within 1 business day.
More: oroom.one/pl/promocja-0-zl
OO4Ecom is the Oroom One solution for online stores and B2B companies where not every order closes in the cart – the customer needs help choosing products, quantities or their own price. The salesperson builds a product offer from the store catalog, sends it under one link, and the customer can accept and pay for it.
What you get:
• offers ready in minutes – cards or a table, photos, video, FAQ, attachments, many languages,
• individual prices and discounts on items and on the total, with terms locked on publication,
• analytics: visits, time, scrolling, clicks, offer forwarding, checkout problems and next-step suggestions,
• moving from the offer to a purchase in your store, without re-entering the order,
• PDF, XLSX and CSV export and funnel events in GA4.
You do not need to change your store: OO4Ecom works alongside it – natively with Shoper, and with other platforms via API, feed or GTM. We confirm the scope of the connection, the data exchanged and any additional work before implementation.
More: oroom.one/pl/promocja-0-zl
A consultation is a 30-minute online conversation about your sales and how Oroom can improve them.
How it works:
1) we agree on a specific date – via the form on oroom.one (“Let's talk”), by email (info@oroom.one) or by phone (+48 600 206 031),
2) we meet online: we ask how you prepare offers, manage customers and communication today, and show solutions using your example,
3) if Oroom fits your process, we help you choose a plan and implementation package.
Who it is for: business owners and people responsible for sales who send offers to customers and want to know what the customer does with them, as well as companies that want to organize their CRM, automations or website.
Do I have to buy anything? No. If you decide Oroom is not for you, you simply say thank you and that is it. We want you to make an informed decision. Bring a sample offer or a description of your sales process to the call – it will make the conversation more specific.
More: oroom.one → Let's talk
The partner program is for companies that build solutions for their clients:
• full-service and digital agencies – you combine strategy, creative and delivery, and Oroom provides the project backend,
• UX/UI agencies – you design interfaces, and Oroom gives you a ready backend and API documentation,
• freelancers and front-end developers – you deliver the complete solution, and Oroom provides the backend and its maintenance.
Roles: the client defines goals and processes, the partner is responsible for strategy, UX/UI, the front end and the client relationship, and Oroom provides the backend with CRM, automations, OO4Ecom offers and AI, supports integration and maintains the system.
Benefits: recurring income from shared clients' subscriptions, technical support from the Oroom team throughout the project and a stronger offering – instead of just a website you deliver a working sales system.
How to join: click “Join the program” on oroom.one/pl/partnerzy or write to info@oroom.one. We will set up a call and discuss the terms of cooperation.
More: oroom.one/pl/partnerzy
We settle with the partner for all invoices issued to shared clients whose interest in Oroom One was initiated by the partner. This covers invoices for the subscription as well as for implementation and adapting Oroom One to the client's needs.
What this means in practice:
• it is not a one-off referral fee – the partner shares in the revenue for as long as the client uses Oroom,
• the more projects you deliver on Oroom, the bigger your recurring revenue,
• you also earn on your own services – design, front end and client service.
The client pays for Oroom according to the price list: a subscription based on scale (catalog and team size), a one-off implementation and separately SMS and WhatsApp. Current prices are on the Pricing page.
Detailed partnership terms, such as the revenue share and settlement method, are discussed individually during a call and set out in the partner agreement.
More: oroom.one/pl/partnerzy
Design: we believe the design should be created as close to the business and the client as possible, so it is usually prepared by the partner. We are happy to take part – we review designs as they are created and advise on solving specific problems, for example an unusual registration, purchase or product presentation process. Preferred design tools are Figma or XD.
Front end:
• the preferred front-end technology is Next.js,
• we provide complete API documentation and prepare missing endpoints needed in the project,
• you decide whether the front end is built by your team or the Oroom team.
Either way, the front-end team has ongoing support from the developers who maintain Oroom One. The backend – CRM, CMS, automations, offers, payments and integrations – is ready, so the project focuses on what the client sees. This makes delivery faster than building the whole system from scratch.
More: oroom.one/pl/partnerzy