Why we built BoostSend
A change in opening hours, a document customers are waiting for, an update about a service. When a business uses several phone numbers, these small tasks become scattered across devices and separate files. Someone has to find the right account, check the recipients and remember what has already been sent.
We developed BoostSend to make that work easier to follow. WhatsApp and Telegram accounts, prepared campaigns and their progress live in one local workspace. The aim is to reduce repetitive handling while keeping the business in control of its communications.
In Morocco, a shop, agency or service business can prepare information from one workstation and write separate French or Arabic campaigns for its customers.
Your team chooses and writes the language of each campaign. Automatic translation is not part of this workflow.
An API connector for your websites and applications
BoostSend includes an API connector that lets your website or business application pass the information needed for a message to the software. Instead of copying customer details between tools, your team can connect a business event to a relevant WhatsApp or Telegram communication.
The trigger, data fields, sending account and approval steps are defined during integration. This is the BoostSend connector, not a claim that BoostSend provides an official WhatsApp API. Account connectivity and platform conditions still apply.
WhatsApp accounts without an application-imposed cap
BoostSend does not set a maximum number of WhatsApp accounts. You can add several numbers, give each a useful name and maintain separate sessions. The sender is chosen when preparing a campaign, so different business activities can use different accounts.
This is what unlimited accounts means here: no account cap imposed by BoostSend. Practical capacity still depends on the computer, connection and platform rules. It does not mean unlimited messages or a way around WhatsApp restrictions. The current WhatsApp connection uses an unofficial engine and may need updates when the platform changes.
Multiple Telegram accounts can also be added, using their own API credentials and the platform’s verification process. This version sends to individual conversations, not Telegram groups or channels.
Keep useful information together
The contact directory holds useful details such as company, reference and internal notes. Lists help identify the people concerned by an update, and one contact can belong to several lists. Excel and CSV imports include a preview to check formats and duplicates before saving.
Centralisation does not mean automatically importing every contact and past conversation from the connected platforms. You choose what to add. Incoming messages are optional for each account; enabling reception makes new private messages available without importing earlier history.
Build an information campaign step by step
Choose the sender and relevant recipients, write the text, add an image or document if needed, then save a draft. Name fields help personalise individual messages without rewriting the same information for each person.
Review the sender, message and recipients before launching. Each recipient gets an individual message in their own conversation. A campaign does not create a group or disclose the recipient list.
Useful examples include an exceptional closure, a service instruction, an availability update or an expected document. Send relevant information to people who should receive it, with their agreement where required. Importing a spreadsheet is not proof of permission to contact its contents.
Schedule and follow progress
The calendar helps organise campaigns over time. A Kanban board shows their progress, while history records sends made from the software. Drafts can be prepared ahead of time, scheduled or paused.
A sent status means the messaging service accepted the message, not that the recipient read it. Uncertain sends need checking rather than an immediate repeat that could create a duplicate.
BoostSend runs locally. The application must remain active and the computer connected for scheduled sends to run. Plan for that before closing the application or letting the workstation sleep.
What changes in everyday work
Continuity is the first benefit. Accounts, drafts and campaign stages are in the same workspace, reducing the need to switch interfaces. Information can be prepared before it needs to go out.
Control is the second. Explicitly selecting the sender and reviewing recipients makes avoidable mix-ups less likely. Progress indicators and pause controls make it easier to intervene.
Consistency is the third. Useful contact details and existing lists support relevant recurring communications. We do not promise a sales result or a fixed amount of time saved; the benefit is a clearer process for repeated tasks.
An optional assistant with human review
An optional AI assistant can suggest replies for review or operate in a configured automatic mode. With review enabled, a person can correct a proposed answer before sending it.
A cloud provider receives the context needed for generation when the assistant is enabled, and its API charges and terms apply separately. A compatible local engine can also be configured. Choose according to your data requirements and check sensitive answers, prices and commitments before relying on them.
Privacy is part of the workflow
The screenshots in this article come from test views of the application. They show no message content, contacts, recipient lists or access keys.
Local data and sessions are stored encrypted. Reception can stay disabled, and contacts marked Do not contact are excluded from new sends. These controls support careful handling but do not replace the company’s own access and usage rules.
A central local application is not automatically a shared cloud workspace. Multiple workstations, staff roles and manager approval processes require a separate assessment if your organisation needs them.
Customer follow-ups and appointment reminders
A quote awaiting a reply, a missing document or an upcoming appointment can each have a dedicated communication scenario. Your application supplies the reference, customer information and relevant date. The message then reflects the actual situation instead of a generic campaign.
The integration must account for cancellations, rescheduling, accepted quotes and completed payments. Stop conditions and status updates are agreed before activation, so a reminder is not sent after the underlying task has already been completed.
Send invoices and quotes from your business software
BoostSend can be used to send invoices and quotes with an accompanying message, document or link as defined by the integration. Your accounting or business application remains responsible for creating the document and maintaining its status.
For example, a completed quote can trigger a message through the chosen account. A later follow-up can depend on the current status in your application. A lack of reply is not evidence that an invoice is unpaid. Sending a PDF through messaging does not, on its own, replace any electronic invoicing system required for your activity.
Plan a reliable API integration
We identify the source application, triggers, necessary data and people responsible for approval. A test scenario checks the recipient, sender, document, schedule and behaviour when the connection is unavailable.
Access protection, duplicate prevention, retries and feedback to your application must be specified for your installation. These capabilities should not be assumed to exist in every connected system. The complete workflow is tested before production use.
A custom workflow for your business
The connector can be the starting point for a custom integration with a website, CRM, booking tool or internal application. Compatibility is assessed case by case. Approval steps, templates and rules for different teams can be included in a scoped development project.
Business follow-ups and information campaigns serve different purposes. Keep them separate while using the same workspace for your WhatsApp and Telegram accounts. Unlimited WhatsApp accounts means no account cap imposed by BoostSend, not unlimited messaging authorised by the platforms.
Common API questions
Does BoostSend create the invoices? The workflow described here transmits and follows up documents produced by your business software, unless a specific development is agreed.
Can messages be automatic? The integration can define automatic triggers, stop conditions and any required approval. The BoostSend installation, sending accounts and connection must be available.
Can an existing website be connected? We assess its technical options and the data it can provide before proposing the integration. Contact hello@boostlab.ma to discuss your workflow.
Talk to Boostlab
Write to hello@boostlab.ma with your activity, current workflow and the repetitive tasks you would like to simplify. We can arrange a demonstration using test data and discuss bespoke development.
Continue with our articles about automating customer requests, Darweb.app and Tymyt time tracking. The links below connect this project to other tools and work by Boostlab.