
A website visitor may ask a question, request a quote, book a call, or send their details. That contact matters, but it is not yet a managed sales opportunity. The business still needs to record the enquiry, assign the follow-up, qualify the need, calculate the offer, and track the outcome.
Bit Assist makes the first step easier. Its multi-channel widget provides messaging apps, live chat services, custom contact forms, FAQs, a knowledge base, WordPress search, booking buttons, and other useful channels in one place. Its contact form can collect structured lead information from any page.
Bit CRM manages what comes next. It is a sales-focused WordPress CRM for organizing leads, contacts, companies, deals, products, invoices, payments, communication, activities, workflows, team access, and client access.
Bit Flows or Bit Integrations can move Bit Assist form submissions into the CRM process, creating a practical route from website conversation to organized sales work.
Bit Assist helps visitors contact a business through their preferred channel. Its custom form can collect names, email addresses, messages, files, ratings, and other selected information.
Bit CRM turns suitable enquiries into structured sales records. It provides six connected modules for Leads, Contacts, Companies, Deals, Products, and Invoices. It also includes tasks, calls, meetings, email history, notes, attachments, links, timelines, tags, custom fields, native workflows, WooCommerce sync, invoice payments, team permissions, a client portal, multi-currency support, data tools, reports, and an MCP server with 57 tools.
Bit Integrations can send mapped Bit Assist data to a Bit CRM action. Bit Flows can watch a submission, route it, create the appropriate CRM record, and continue with other actions.
Website communication and sales management cover different parts of the same customer journey. Bit Assist lets a visitor open a floating widget without leaving the page. They can choose WhatsApp, Messenger, Telegram, a live chat service, a booking option, or a custom form. FAQs, the knowledge base, and WordPress search can answer common questions first.

Bit Assist can store contact form responses, email them to a selected address, or send them to a webhook. This is where a sales process can begin.
Bit CRM gives the enquiry an owner, status, source, history, and next action. After qualification, the lead can become a contact, company, and deal containing the offer, value, stage, invoice, and payment history.
The complete path looks like this:
| Stage | Tool | Main purpose |
| Visitor engagement | Bit Assist | Offer contact channels, answer common questions, and collect structured enquiries |
| Data handoff | Bit Integrations or Bit Flows | Map the submitted data and send it into the next business process |
| Sales management | Bit CRM | Qualify the lead, manage follow-up, track the deal, prepare the invoice, and maintain the relationship |
The visitor gets an easy way to begin, while the sales team gets a system for handling what follows.
The clearest connection begins with the Bit Assist custom contact form. It can ask for a name, email, phone number, company, service, budget range, preferred contact method, and message. Its webhook field allows the submission to trigger an automation.

Bit Integrations supports Bit Assist as a trigger. It generates a webhook URL that can be added to the Bit Assist custom contact form. After a test submission is captured, the form fields can be mapped to the selected action.
This route suits a simple process such as:
Bit Assist form submitted → Create a lead in Bit CRM
The workflow can map the visitor’s name, email, phone, company, source, and message to CRM fields, producing a consistent lead record without re-entry.

Bit Flows includes a Bit Assist trigger with the Watch Submission event. Its webhook URL is placed in the Bit Assist form, and a test submission provides the data for field mapping.
Bit Flows suits a process that needs conditions, routers, delays, parsers, API requests, AI Agent, Human in the Loop, or several actions.
A practical flow could be:
Bit Assist submission → Condition → Router → Create Bit CRM lead → Create task → Send notification

The flow could also check whether an enquiry has enough information, send selected requests for human review, or route support messages elsewhere. The logic should follow the business’s qualification rules.
Bit CRM’s features cover the complete sales path rather than only storing contact details.
| Sales area | Included capabilities |
| Lead intake | Lead records, source and status, owners, tags, custom fields, activities, timelines, CSV import, and lead conversion |
| Customer relationships | Contacts, companies, linked records, addresses, currencies, email history, notes, files, links, and complete activity context |
| Opportunity management | Deal list and Kanban views, custom stages, probabilities, values, owners, dates, sources, types, and connected products |
| Products and pricing | Local products and services, WooCommerce products, custom line items, quantities, prices, costs, discounts, taxes, and calculated totals |
| Invoicing and payment | Deal-based invoices, branding, live preview, PDFs, public links, email delivery, full or partial WooCommerce payments, and balance history |
| Sales activity | Global and record-level tasks, calls, and meetings with ownership, status, dates, notes, and attachments |
| Automation | CRM triggers, conditions, If and If-Else branches, delays, emails, field updates, tags, activities, lead conversion, webhooks, and logs |
| Team and client access | Detailed staff roles, record ownership, a white-label client portal, module controls, action controls, and field-level permissions |
| Administration | Custom fields, configurable layouts and columns, search, filters, bulk actions, multi-currency settings, history, Recycle Bin, and transfer records |
| Connected tools | WooCommerce, Bit Form, Bit SMTP, Bit Integrations, Bit Flows, and an MCP server for supported AI clients and agents |
These capabilities remain connected as a lead becomes a customer.
The Leads module is for prospects who still need qualification. A lead can hold contact and company information, addresses, source, status, owner, currency, tags, and custom fields. The team can distinguish a pricing enquiry from a support request and assign it correctly.

Tasks, calls, meetings, emails, notes, files, links, upcoming activities, and the timeline keep history and next steps with the lead.
Search, quick filters, advanced filters, sorting, configurable columns, pagination, bulk actions, and module-specific tags help teams manage larger lead lists. Supported CRM modules also include CSV import and export for moving existing data or preparing external reports.
When the enquiry becomes a real business relationship, Bit CRM can convert the lead into a contact and company. A deal can also be created during the same process when an active opportunity already exists.
Conversion mapping controls how standard and custom lead fields move into the new records. Supported ownership, tags, activities, notes, files, and links can move with the lead. The team does not need to rebuild the customer profile after qualification.

Contacts represent individual people. Companies hold the organizations connected to them. This structure supports several people in one purchase or several opportunities for one company. Each profile can bring together related deals, activities, communication, addresses, tags, currency, notes, files, links, and other selected information.
Qualified opportunities belong in the Deals module. Deals can be reviewed in a detailed list or moved visually on a drag-and-drop Kanban board. Custom pipeline stages, stage probabilities, and Open, Closed Won, or Closed Lost categories show where each opportunity stands.
A deal can include its contact, company, owner, source, type, stage, probability, currency, amount, start date, expected close date, description, tags, products, activities, and invoices.

The team can see who owns the opportunity, what it may be worth, what is being offered, and what action is due. A project request, consulting package, wholesale order, or recurring service becomes measurable sales work.
Bit CRM includes reusable product records for goods and services. A product can store a name, SKU or code, type, brand, description, unit price, cost price, tax, status, tags, and custom data. WooCommerce products can also be used without recreating them locally.
When a product is added to a deal, the salesperson can set the description, price, quantity, discount, and tax for that opportunity. Custom line items can cover something that is not already saved. Bit CRM calculates line totals, subtotal, total discount, tax, and grand total.

The visitor’s request becomes an itemized offer rather than a rough figure in a message thread.
An invoice can be created from the related deal. Contact details, company information, currency, and product line items remain connected to the opportunity.
The invoice builder supports the business logo, invoice numbering, issue and due dates, payment terms, sender and billing details, formatted content, notes, terms, discounts, taxes, and live preview. The completed invoice can be emailed, downloaded as a PDF, opened through a public link, or shared in the client portal.

Payments use WooCommerce checkout and the payment gateways already enabled on the store. The business can request the full balance or allow several partial payments with a fixed or percentage-based minimum. Payment History records each transaction and recalculates the paid and due amounts. The invoice can move through Draft, Sent, Partially Paid, Paid, or Overdue status.

The enquiry, customer, deal, offer, invoice, and payment history stay connected.
Bit CRM provides separate modules for tasks, calls, and meetings. Activities can be created from the relevant CRM record, from the global activity area, or through automation.

Tasks can include an owner, due date, priority, details, status, notes, and attachments. Calls and meetings can be scheduled or recorded with their dates, responsible users, status, and related records. Pending Activities on the dashboard helps the team find upcoming work across the CRM.
Individual users can connect email through IMAP so matching conversations appear with relevant records. Bit SMTP handles outgoing CRM, workflow, and invoice emails. Notes, attachments, links, timelines, and CRM-wide History preserve further context.
After the Bit Assist handoff, Bit CRM’s native workflow builder handles repeatable work inside the CRM.
A workflow can start from supported record events, field changes, tag changes, or deal-stage changes. Conditions and If or If-Else branches decide which route should run. Delays can wait before the next step.

Actions include managing tags, creating tasks, calls, meetings, and notes, sending emails, updating fields, converting leads, moving supported records to the Recycle Bin, and sending webhooks. Logs show executed nodes and success or failure.
A new website lead could receive a source tag and task. A later stage change could schedule a meeting or notify another system.
Bit Assist and Bit CRM can support different parts of a WooCommerce customer journey.
Inside the widget, Bit Assist can show WooCommerce order information such as shipping status, quantity, amount, billing name, and shipping name. Customers can also ask questions through available channels.
Bit CRM connects sales data with WooCommerce. Customers can be matched to CRM contacts by email when orders are created or updated. Contacts can receive tags based on purchased products or coupon codes. WooCommerce products remain available for deals and invoices, while invoice payments use the store checkout.
This connects customer-facing support with structured sales and customer records.
CRM users can have different permissions. Administrators can control access to modules and actions such as viewing, creating, updating, deleting, importing, and exporting records. Settings for workflows, email, integrations, currency, data, and CRM users can be restricted separately. Record ownership helps clarify responsibility.

The client portal gives approved contacts a separate login without exposing the WordPress dashboard. Access can include the portal dashboard, contact profile, calls, meetings, notes, deals, and invoices.

Module, action, and field-level settings control what each client can use, view, or edit. A customer may update an address while internal notes, ownership, probability, and private fields remain hidden.

White-label controls can use the business name and logo. Clients can review shared information, download invoices, and follow payment links.
Leads, Contacts, Companies, Deals, and Products can each use their own custom fields. Available formats include text, multiline text, number, date, dropdown, radio, checkbox, multi-select, and other supported types. Fields can be arranged into movable sections with one-column or two-column layouts.

The business can set a home currency and enter exchange rates manually for other currencies. Currency can pass from a contact or company to its deals and invoices.
Transfer History records imports and exports. Deleted records can be restored from the Recycle Bin, and administrators can manage workflow log retention.
The dashboard summarizes leads, contacts, companies, deals, and invoices. It also shows pending activities and reports covering pipeline performance, lead sources, invoice status, and top products based on paid CRM invoices.
Bit CRM includes an MCP server. Model Context Protocol gives compatible AI clients and agents a structured way to use approved tools from another system.

The Bit CRM MCP server currently provides 57 tools for supported operations involving leads, contacts, companies, deals, products, invoices, tasks, calls, meetings, tags, workflows, and related CRM information.
After connection, a supported client can find and summarize records, create or update supported data, prepare activities, manage tags, or work with invoice information. Results depend on the exposed tools and client configuration.
MCP is separate from the Bit Assist handoff. It gives supported AI clients and agents a tool-based way to work with CRM data.
This process fits WordPress businesses that receive enquiries online and need a structured way to handle them after the first contact.
It can work well for:
Bit Assist captures the first contact. Bit CRM provides the records, pipeline, commercial tools, controls, and history for managing suitable enquiries.
A lead requires response, qualification, ownership, follow-up, and a clear outcome. Bit Assist provides messaging channels and a customizable contact form. Bit Integrations handles a direct handoff, while Bit Flows supports detailed lead routing. Bit CRM then manages the journey from lead to deal, invoice, payment, and client access.
Together, they connect website conversations with organized sales work.
Yes. Bit Assist includes a custom contact form inside its floating widget. The form can collect selected visitor details, store responses, send entries by email, and pass submission data to a webhook.
You can use Bit Integrations for a direct trigger-and-action handoff or Bit Flows for a multi-step workflow. In both cases, a webhook URL is added to the Bit Assist custom form so submitted fields can be captured and mapped to the CRM process.
Use Bit Integrations when the submission only needs a simple handoff to a selected action. Use Bit Flows when the process needs several actions, routing, conditions, delays, data parsing, AI Agent, human approval, API requests, or other advanced workflow logic.
Bit CRM can manage qualification data, ownership, activities, contact and company conversion, deals, pipeline stages, products, calculations, invoices, payments, communication history, workflows, team permissions, and client portal access.
Yes. Leads can be qualified and converted into connected contacts and companies, with an optional deal. Companies can hold related people, opportunities, activities, and other sales context, making the structure useful for B2B teams.
Yes. Bit CRM can match WooCommerce customers with CRM contacts, apply supported product or coupon-based tags, use WooCommerce products in deals and invoices, and collect invoice payments through WooCommerce checkout.
Yes. Administrators can enable a separate client portal for approved contacts. Portal, action, and field-level controls determine which contact data, activities, deals, and invoices each client may view or edit.
It exposes 57 structured tools for supported CRM operations. Compatible AI clients and agents can use those tools to find, summarize, create, or update supported records and activities after the required connection is configured.

