Less busywork.
More possibility.
From finding the right business to handling the next reply, see exactly what your Ai sales employee can do — and the work it takes off your plate.
What it does.
Why it helps.
Every row pairs a feature with its practical productivity benefit and the system behaviour behind it. Browse the complete directory or jump to the part of the workflow that matters to you.
228 features across 14 categories
Business Profiles & offers
Give Lido Ai a clear, reusable brief for your business.
| Feature | Productivity benefit | How it works |
|---|---|---|
| Multiple Business Profiles | Run outreach for different businesses or offers from one account. | Save separate profiles and link the appropriate profile to each campaign. |
| Business identity | Keep your outreach recognisable. | Provide your business name, website and sender identity as the factual basis for emails. |
| Sender name and role | Make introductions come from the right person. | Store the sender’s real name and role for grounded greetings and signatures. |
| Products and services | Give the Ai an accurate offer to work with. | Separate product and service information supplies the drafting context. |
| Value proposition | Explain the useful difference your business makes. | Save the commercial benefits that can support prospect-specific sales angles. |
| Target audience | Focus the Ai on suitable buyers. | Describe the audience alongside campaign targeting and prospect research. |
| Promotional offers | Use genuine offers where they strengthen the pitch. | Saved promotional details may be included without inventing discounts or deadlines. |
| Commercial terms | Help replies explain how your offer works. | Store seller-approved prices, commissions and other terms as factual context. |
| Preferred call to action | Guide the next step you want prospects to take. | Supply your preferred CTA as part of the profile brief. |
| Reply FAQs | Reduce repetitive explanations in conversations. | Saved answers provide grounded information for common prospect questions. |
| Additional business context | Give the Ai useful details beyond the main fields. | Add supplementary information that can inform drafting and reply handling. |
| Ten email tones | Choose a voice that suits your business. | Select Professional Authority, Friendly Consultative, Direct Results Driven, Premium Strategic, Casual Conversational, High Energy Growth, Local Trust Building, Executive B2B, Bold Sales Driven or Educational Advisory. |
| Website analysis and autofill | Spend less time building your Business Profile. | Ai website analysis suggests profile fields for you to review and save. |
| Review suggested profile information | Keep control over what represents your business. | Analysis suggestions are applied to the form; saving the profile is a separate user action. |
Campaign planning & lead sourcing
Find relevant businesses and build focused prospect lists.
| Feature | Productivity benefit | How it works |
|---|---|---|
| Profile-linked campaigns | Keep each campaign aligned with the right offer. | Campaign setup requires a Business Profile and carries its context through the workflow. |
| Business-category targeting | Look for the types of business most likely to need your offer. | Define a sector or business category for the prospect search. |
| Location targeting | Focus outreach on your chosen area. | Search by a specified place or area within the chosen country. |
| Six-country campaign selection | Reach prospects in supported markets. | The campaign form supports the UK, US, Australia, Canada, Ireland and New Zealand. |
| Ai campaign ideas | Get help identifying useful prospect categories. | Ai suggests specific business types and explains their commercial fit with your offer. |
| Campaign idea refinement | Turn a broad sector into more useful searches. | Related category suggestions can refine an existing targeting direction. |
| Campaign idea relevance scoring | Compare suggested audiences before choosing. | Suggested search ideas include fit scores, reasoning and an outreach angle. |
| Existing-campaign awareness | Reduce repeated targeting suggestions. | Idea generation receives existing sector and area combinations to avoid repetitions. |
| Business listing acquisition | Build a prospect list without copying contacts by hand. | Business searches retrieve listing details such as company name, website and available contact information. |
| Duplicate lead detection | Avoid reacquiring the same business unnecessarily. | Identity checks compare available email, website, place identity and business/address information within your account. |
| Deleted-lead history | Reduce repeat acquisition after cleaning your lists. | Lead identity history can remain after a live lead is deleted. |
| Unique-lead credit charging | Keep acquisition costs tied to accepted new prospects. | Saved lead acquisition and its associated credit event are recorded together. |
| Campaign creation credit confirmation | See the acquisition cost before proceeding. | The campaign workflow presents its credit confirmation before accepting the purchase action. |
| Campaign management | Review your campaigns in one place. | Campaign cards link to their saved leads, current status and management actions. |
| Campaign deletion | Remove campaigns you no longer need. | Owned campaign deletion clears associated live outreach records while retaining account learning history. |
| CSV lead export | Use your prospect list outside the workspace. | Export company name, website and email address from a campaign. |
Contact discovery & verification
Prepare a usable contact address before outreach starts.
| Feature | Productivity benefit | How it works |
|---|---|---|
| Website email discovery | Find contact details beyond the original business listing. | The discovery stage checks the business website for email candidates. |
| Contact-page exploration | Improve the chance of finding a relevant address. | The website crawler follows suitable internal pages, including contact-style routes. |
| Multiple email candidates | Avoid relying on the first address found. | Candidate addresses and their sources are saved for selection and verification. |
| Email extraction and normalisation | Reduce malformed or repeated contact data. | Discovered email strings are cleaned, normalised and checked before further processing. |
| Candidate classification | Help the system distinguish types of address. | Address patterns contribute to candidate categorisation and selection. |
| Public website crawling checks | Keep website discovery focused on appropriate destinations. | Crawler rules validate public URLs and constrain page traversal and redirects. |
| Mail-domain preflight | Catch basic address problems early. | Local checks examine email syntax and domain mail records before provider verification. |
| Disposable and placeholder screening | Avoid obviously unsuitable contact addresses. | Known disposable domains and placeholder-style domains are flagged in preflight. |
| Independent email verification | Reduce preventable outreach failures. | Candidate addresses can be checked using the configured verification provider. |
| Verification result classification | Make address suitability visible to the workflow. | Provider outcomes are mapped into usable, risky or invalid verification states. |
| Primary address selection | Give each lead one selected outreach recipient. | Candidate scoring and verification outcomes determine the primary email address. |
| Verification-based blocking | Keep unusable contacts out of the send workflow. | Leads that fail the required verification conditions are held or blocked. |
| Discovery and verification retries | Recover from temporary processing problems. | Worker retry state and next-attempt times support another attempt where appropriate. |
| Limited-context recovery | Keep an eligible lead moving when research is restricted. | Supported failure recovery can continue with known facts and require review of the first draft. |
Prospect research & sales intelligence
Give every email a reason to be relevant.
| Feature | Productivity benefit | How it works |
|---|---|---|
| Prospect business research | Reduce the time spent investigating each business. | The research stage assembles available website and search context for the lead. |
| Business summaries | Help the Ai understand what the prospect actually does. | Research stores a concise description of the business. |
| Service summaries | Connect your offer with the prospect’s activity. | The research record includes relevant services and business activity. |
| Customer and audience context | Frame benefits around the people the prospect serves. | Research can identify supported target-customer groups. |
| Commercial signals | Spot useful context for a sales approach. | Available business signals can inform the proposed outreach angle. |
| Personalisation points | Make relevance more specific than a company-name insertion. | Supported prospect details are selected as personalisation material. |
| Potential pain-point hypotheses | Explore possible needs without asserting unverified problems. | Likely pain points are treated as hypotheses rather than admitted prospect facts. |
| Suggested outreach angles | Give the first draft a relevant starting direction. | Research proposes an angle connecting the prospect with the seller’s offer. |
| Research confidence | Adjust how specific a claim should be. | Confidence context accompanies the research supplied to drafting. |
| Saved research sources | Keep supporting context available to the workflow. | Research source records and cached page information can be retained for reuse. |
| Research text cleanup | Keep evidence noise out of customer-facing messages. | Source and citation artefacts are cleaned from research text and prohibited in final email copy. |
Personalised outreach & follow-ups
Turn business facts into useful sales conversations.
| Feature | Productivity benefit | How it works |
|---|---|---|
| Prospect-specific first emails | Reduce generic introductions that simply repeat your profile. | The first-email brief asks for one supported connection between the prospect and a practical seller benefit. |
| Benefit-led selling | Explain why this business might care. | Drafting translates relevant profile facts into a potential benefit instead of a catalogue of features. |
| Selective offer details | Keep emails focused and readable. | The Ai chooses the seller details that support the primary sales angle. |
| Grounded personalisation | Make outreach relevant while keeping claims accurate. | Prospect facts come from supplied research and seller facts from approved business context. |
| Short, natural subjects | Make the purpose of an email easier to recognise. | Subject rules favour concise, relevant wording and exclude clickbait-style claims. |
| Concise plain-text copy | Produce emails that are easy to read and edit. | Drafting uses short email bodies and rejects HTML, unresolved placeholders and unwanted markdown. |
| One clear next step | Make it easier for a prospect to answer. | Each cold email uses one low-friction CTA rather than several unrelated requests. |
| Genuine sender signatures | Maintain a consistent business identity. | Sign-offs use the provided sender details without inventing a person or role. |
| Natural opt-out wording | Give prospects a simple way to decline. | Cold outreach includes a short, human way to request no further follow-up. |
| Country-aware spelling | Make copy feel natural for the target market. | Drafting adapts spelling where the prospect or campaign country is clear. |
| Ai quality review | Catch weak or unsupported drafts before they progress. | A second review can pass, revise or reject the generated message. |
| Commercial relevance review | Improve a polished email that still lacks a useful pitch. | The first-email reviewer must revise profile summaries and unclear reasons to care. |
| Deterministic email checks | Catch formatting and content problems consistently. | Validation checks word limits, placeholders, link domains and high-risk hype phrases. |
| Seller-domain link guard | Keep generated links tied to the supplied business website. | Outgoing links are checked against the Business Profile website domain. |
| Finite follow-up sequences | Continue outreach without planning every touch manually. | The cold outreach strategy supports a bounded sequence of up to six emails. |
| Distinct follow-up roles | Give later emails a purpose beyond “just checking in”. | Sequence steps direct alternative use cases, benefits, reduced friction and light re-engagement. |
| Earlier-email awareness | Reduce repetitive subjects, openings and pitches. | Later drafting receives previous outreach in chronological order. |
| No-new-angle fallback | Avoid manufacturing a new selling point when none is supported. | A later touch can use a modest permission or interest check instead of invented novelty. |
| Final close-the-loop email | Bring unanswered cold outreach to a clear end. | The last sequence step has specific final-touch wording and no promise of another follow-up. |
Ai Training, fresh redrafts & undo
Shape the voice while keeping control over changes.
| Feature | Productivity benefit | How it works |
|---|---|---|
| Learning from saved human edits | Improve the starting point for later drafts. | Saved user changes contribute account-specific writing-style patterns. |
| Style adaptation across campaigns | Use your preferences beyond one lead. | Account-level style context can inform later outreach and reply drafts. |
| Length and paragraph preferences | Make future messages closer to your preferred format. | Style analysis can learn patterns in body length and paragraphing. |
| Greeting and sign-off preferences | Guide how your messages open and close. | Saved editing patterns can shape subsequent greetings and signatures. |
| Subject-only learning | Adjust subject style without treating an untouched body as your writing. | A subject change can contribute subject preferences independently of body edits. |
| Explicit writing instructions | Tell Lido Ai how you want emails written. | Ai Training accepts saved user preferences such as shorter paragraphs or a warmer tone. |
| Separate outreach and reply preferences | Tailor your voice to the type of message. | Training instructions can apply to outreach, replies or all outgoing email. |
| Saved sales concepts | Give the Ai useful ideas to consider. | Store account concepts that may guide an angle when the current facts support them. |
| Concept and preference controls | Keep your active guidance relevant. | Enable, disable or delete saved instructions and concepts. |
| Before-and-after edit history | See what your writing preferences are based on. | Ai Training displays saved original and edited wording. |
| Learning history cleanup | Remove examples you no longer want used. | Delete individual edit examples or clear the learning history. |
| Learning retained after campaign deletion | Keep useful account preferences while tidying your workspace. | Deleting a campaign does not automatically remove its account training edits. |
| Request Ai Redraft | Replace an unsatisfactory editable outgoing email with a fresh draft. | The action is available for approval drafts, ready or scheduled outreach, and editable conversation replies. |
| Tone-directed redrafting | Choose a different voice for one email. | The popup offers the same ten tones as Business Profiles without changing the saved profile tone. |
| Complete rewrite instructions | Get new copy rather than a lightly polished version. | The redraft brief rebuilds the subject, greeting, opening, structure, language, CTA and sign-off while preserving facts. |
| Reused-copy checks | Avoid paying for a substantially recycled draft. | Unchanged subjects and excessive reused body wording are rejected rather than saved as a successful redraft. |
| Two-credit redrafts | Know the cost before asking for another version. | A successful saved redraft costs 2 credits; failed requests do not deduct the redraft charge. |
| Undo Redraft | Restore the previous wording if you prefer it. | Undo restores the prior subject, body and CTA; it does not refund credits. |
| Redraft undo history | Step back through recent versions of the same email. | Up to ten previous redrafts can be retained for that email. |
| Redrafts excluded from Ai Training | Keep machine-written alternatives out of learned human preferences. | Redraft and undo operations do not record training examples or change your Business Profile tone. |
Starting outreach & approval control
Choose how much work Lido Ai handles on its own.
| Feature | Productivity benefit | How it works |
|---|---|---|
| Manual approval mode | Review applicable drafts before sending. | Manual execution holds messages for an explicit user approval action. |
| Autonomous mode | Reduce the routine work of progressing qualifying messages. | Eligible drafts can pass quality gates and move through scheduling without individual approval. |
| Global Ai Mode control | Set a preferred mode across your account. | The global control applies the selected execution mode through the supported campaign and lead paths. |
| Individual lead overrides | Handle an important prospect differently. | A lead-specific setting can override the inherited campaign mode. |
| Return to inherited mode | Keep exceptions manageable. | A lead can be set to follow the global or campaign mode again. |
| Optional Auto Start | Reduce repetitive clicking when acquiring leads. | The Auto Start setting can begin eligible leads automatically. |
| Start individual outreach | Choose when a specific lead begins. | Start Outreach moves an eligible owned lead into the processing pipeline. |
| Start a campaign’s eligible leads | Begin a focused batch together. | Supported campaign controls start its available leads. |
| Start all available lead outreaches | Save time when several campaigns are ready. | The bulk start action progresses eligible waiting leads across the account. |
| Stop further sending for a lead | Pause outreach when you need to take control. | Stop controls update lead state and prevent further eligible automated sending. |
| Draft editing before approval | Correct wording or details before giving the go-ahead. | Editable outreach subjects, bodies and CTAs can be saved for review. |
| Ready-draft editing | Make changes before the email is scheduled. | The ready-to-send editor checks the current revision and processing state. |
| Scheduled outreach editing | Improve copy while it waits for its sending slot. | Editing is permitted only before sending starts; a normal save retains the scheduled slot. |
| Redraft approval reset | Review the new wording before it goes out. | A successful redraft returns to approval; scheduled outreach is scheduled again after approval. |
Sending accounts, scheduling & delivery
Move email through a controlled sending workflow.
| Feature | Productivity benefit | How it works |
|---|---|---|
| SMTP sending account connection | Send using your configured business email identity. | Connect SMTP host, port, authentication and encryption settings. |
| Multiple sending accounts | Associate the right mailbox with each Business Profile. | Accounts can be linked to profiles, enabled, disabled and selected as defaults. |
| Connection testing | Find mailbox setup problems before outreach runs. | SMTP and inbox testing record whether the configured connection works. |
| Sending account archiving | Retire an account without keeping it eligible to send. | Archived accounts are excluded from the available sending identities. |
| Encrypted stored credentials | Protect saved mailbox secrets at rest. | Mailbox credential storage uses authenticated encryption. |
| IMAP inbox connection | Bring prospect replies back into the platform. | Configure and test the inbox account used for reply monitoring. |
| Sending timezone | Run outreach on a chosen local clock. | Scheduling uses the account timezone for local sending windows. |
| Allowed sending days | Avoid sending on days you have excluded. | The scheduler normalises candidate slots into the enabled weekdays. |
| Daily sending windows | Keep outreach within your chosen hours. | Local start and end times constrain when an email can be scheduled and sent. |
| Minimum sending gap | Avoid sending all emails at once. | A configured minimum interval separates mailbox send activity. |
| Hourly sending caps | Control short bursts of email activity. | Rolling-hour limits constrain eligible sending slots. |
| Daily sending caps | Keep volume within your chosen account limit. | Local-day limits are applied when calculating and checking sending eligibility. |
| Humanised send timing | Make the schedule less mechanically uniform. | Eligible slots include controlled timing variation within the account rules. |
| Shared mailbox pacing | Avoid separate queues independently overrunning one mailbox. | Outreach and conversation activity are considered in mailbox timing checks. |
| Displayed local schedules | See when an email is expected to leave. | Scheduled local time and timezone are stored alongside the UTC sending timestamp. |
| Send-time rechecks | Catch changed conditions before delivery is attempted. | The sender rechecks workflow state, limits and current eligibility. |
| Out-of-window rescheduling | Recover when a planned slot is no longer valid. | Messages can be moved to a later eligible sending window. |
| Reply priority | Keep active conversations moving ahead of more cold outreach. | Cold send eligibility checks account-level conversation work awaiting processing. |
| SMTP attempt records | Make delivery problems easier to investigate. | Send attempts retain response and outcome information for the workflow. |
| Temporary failure retries | Recover from transient recipient-server problems. | Eligible first-email failures offer additional user-requested attempts. |
| First-email retry and refund choice | Choose how to resolve an eligible failed introduction. | The supported failure path allows up to ten additional tries before offering an eligible delete-and-credit refund option. |
| Uncertain-delivery protection | Reduce the chance of an accidental duplicate email. | Uncertain delivery states block automatic retransmission until resolved. |
Reply monitoring & conversation intelligence
Keep the conversation moving after the first response.
| Feature | Productivity benefit | How it works |
|---|---|---|
| Background inbox monitoring | Reduce manual checking for prospect replies. | The IMAP worker polls enabled accounts and tracks progress through mailbox messages. |
| Reply-to-thread matching | Bring the right reply into the right lead’s conversation. | Message identifiers, references and recipient matching help link inbound and outbound email. |
| Plain-text reply extraction | Make received email easier for the Ai to interpret. | Mail parsing handles common encodings, HTML/text parts and quoted-reply cleanup. |
| Duplicate inbound protection | Avoid processing the same mailbox item repeatedly. | Mailbox identity and message progress checks detect already processed inbound items. |
| Human-reply recognition | Switch from cold outreach to a conversation workflow. | A matched reply can trigger reply intelligence and conversation handling. |
| Out-of-office recognition | Avoid treating an automated absence message as a sales reply. | Auto-response headers and message patterns identify out-of-office messages. |
| Hard-bounce classification | Recognise permanent delivery problems. | Bounce content and SMTP-style status indicators inform permanent-failure handling. |
| Soft-bounce classification | Distinguish temporary problems from permanent failures. | Temporary status codes and mailbox conditions inform soft-bounce handling. |
| Spam complaint recognition | Respond to explicit complaint signals. | Complaint feedback and abuse-report patterns trigger protective handling. |
| Opt-out recognition | Stop eligible further sending when a prospect asks. | Unsubscribe and removal requests can create suppression and cancel pending work. |
| Not-interested recognition | Avoid continuing an unwanted sales conversation. | A negative-interest outcome can close the conversation without another sales response. |
| Not-now recognition | Respect a prospect who is not ready. | Recognised deferrals can pause the conversation rather than force a reply. |
| Positive-interest classification | Help the system recognise an engaged prospect. | Reply intelligence classifies interest and records the relevant outcome. |
| Question and objection handling | Reduce time spent sorting the type of reply. | Ai analysis distinguishes questions, objections, pricing queries and information requests. |
| Reply confidence scoring | Help separate clear situations from uncertain ones. | Intent confidence is considered alongside quality and execution mode. |
| Grounded Ai conversation drafts | Prepare an answer using the right seller and thread context. | Reply generation receives inbound content, prior messages, business facts and approved handover context. |
| Settled-answer continuity | Avoid asking a clarification the prospect already answered. | Conversation prompts treat previous questions and supplied answers as established state. |
| Consistent thread identity | Keep an existing conversation recognisable. | Reply rules preserve the seller identity already used in the thread. |
| Quality-reviewed replies | Catch unsupported or unhelpful answers. | A review can pass, revise or reject the conversational draft before progression. |
| Autonomous reply gate | Reduce routine approvals only when the reply qualifies. | Autonomous progression checks confidence, quality, intent and handover requirements. |
| Human handover | Bring you in when the Ai lacks facts or needs judgement. | Unclear requests, missing information and selected intents can require human intervention. |
| Handover context and recovery | Help the Ai continue after you supply the missing information. | Add seller context and instructions, then request another grounded response for review. |
| Meeting-request handover | Keep control of a prospect’s request to meet. | Meeting intent is recognised and referred for human handling. |
| Threaded conversation sending | Keep an approved response connected to the email exchange. | Reply sending preserves message references and parent-message information. |
Lead Manager & everyday productivity
See each prospect’s progress and act from one workspace.
| Feature | Productivity benefit | How it works |
|---|---|---|
| Compact lead cards | Scan the prospect list quickly. | Cards show the business, campaign context and current status. |
| Lead search | Find a particular business without scanning every card. | Search by lead name or reference. |
| Status filtering | Focus on prospects that need a particular action. | Filter the Lead Manager list by the supported status choices. |
| Campaign context on leads | Recognise which offer a prospect belongs to. | Campaign names appear alongside lead information. |
| Lead journey status | Understand what the system is doing now. | Discovery, verification, research, drafting, approval and sending stages are presented in the lead view. |
| Plain-language progress messages | Spend less time interpreting internal stage names. | The interface explains the current work or attention required for the business. |
| Full email thread view | Review the exchange before taking action. | Lead Manager displays the lead’s outgoing and received conversation messages. |
| Draft, approval and schedule visibility | Know which emails still need action. | Message and workflow status distinguish review, queued and sent work. |
| Conversation reply editing | Make an applicable answer your own. | The composer supports editing and saving a mutable reply before approval. |
| Approve a conversation reply | Control when a reviewed answer can progress. | An explicit approval action moves an eligible reply into the scheduling workflow. |
| Mark a lead converted | Record a successful sales outcome. | Conversion controls update the conversation outcome and stop relevant automated outreach work. |
| Close a conversation | Finish an exchange deliberately. | Closing controls update lifecycle state and prevent eligible further conversation sending. |
| Delete individual leads | Keep your workspace focused. | Owned lead deletion removes the lead and associated live pending outreach data. |
| Action-focused dashboard | See where your attention will make a difference. | The dashboard links to pending drafts, handovers and sending issues. |
| Pipeline dashboard counts | Monitor your current email activity at a glance. | Dashboard cards show ready work, campaigns, scheduled emails, sent emails and received replies. |
Credits, billing & account reporting
See what the work costs and where credits go.
| Feature | Productivity benefit | How it works |
|---|---|---|
| Pay-as-you-go credit packs | Buy capacity when you need it. | One-off USD credit packs fund the platform’s credit-based actions. |
| No monthly subscription requirement | Keep expenditure aligned with your use. | The current purchase flow sells credit packs rather than a recurring monthly plan. |
| Eligible signup credits | Try the workflow before buying a pack. | Eligible new verified accounts receive the configured introductory credit award. |
| Live action pricing | Check current credit costs before using the service. | Public pricing and billing use the configured process-cost values. |
| Visible credit balance | Know how much capacity remains. | The workspace and billing views display the account’s current credits. |
| Credit activity history | Understand individual deductions and additions. | Transactions record credit amounts, balances, references and action notes. |
| Lifetime credit totals | See cumulative purchase and usage activity. | Credit summaries track purchased, used and remaining totals. |
| Monthly credit usage | Review recent spending over time. | Billing provides month-based usage information. |
| Campaign credit reporting | Compare the credit use associated with campaigns. | Campaign usage is aggregated from the credit activity records. |
| Stripe checkout | Purchase credits through the configured payment flow. | Credit packs create a Stripe Checkout session in the selected payment environment. |
| Payment confirmation processing | Reduce manual credit allocation after purchase. | Stripe webhook processing validates events and applies supported credit awards. |
| Duplicate-payment protection | Avoid crediting one payment event twice. | Webhook and operation references support idempotent payment processing. |
| Invoice access | Keep purchase records available. | Billing lists invoices and provides invoice download access. |
| Eligible failed-send refunds | Recover the sending charge for known unsuccessful attempts. | Known failed SMTP attempts can generate a matched credit refund event. |
| Eligible lead failure refunds | Resolve supported acquisition or first-email failures. | Eligibility checks determine whether deletion and the stated credit refund are available. |
Account access, support & data controls
Manage your account and get help when needed.
| Feature | Productivity benefit | How it works |
|---|---|---|
| Verified signup | Confirm ownership of the account’s email address. | Account activation uses email verification and a verification link workflow. |
| Account sign-in | Access your own campaigns and conversations. | Authenticated sessions scope the account workspace. |
| Password reset | Recover access to your account. | Reset links use expiring tokens and rate-limited sending. |
| Account profile management | Keep your account details current. | The account page provides the supported identity and account settings. |
| Getting-started guidance | Find the next useful step after signup. | Welcome and next-step components guide setup and early campaign actions. |
| In-app support chat | Ask for help from within your workspace. | Support messages are associated with your account and shown through the chat interface. |
| Welcome support message | Give new users an immediate support starting point. | The verification workflow can create the platform’s configured welcome message. |
| Contact form | Reach the team before or after joining. | The public website provides a contact route with anti-spam checks. |
| Password-protected account deletion | Remove an account you no longer want to use. | The permanent deletion action requires account authentication and password verification. |
| Delete stored email messages | Control stored platform email content. | An account action permanently removes eligible stored email-message data. |
| Policy pages | Review the platform’s stated rules and data information. | Privacy, terms, data processing, anti-spam and credit-policy pages are linked publicly. |
Programmatic controls & operational behaviour
The mechanisms supporting the customer-facing workflow.
| Feature | Productivity benefit | How it works |
|---|---|---|
| Staged background processing | Let the workflow progress without keeping a page open. | Separate processing stages handle discovery, verification, research, generation, queues, sending and replies. |
| Scheduled worker execution | Run recurring platform work automatically. | Cron-compatible workers and the external webcron runner execute the supported pipelines. |
| Authenticated workflow actions | Keep controls tied to the account using them. | Server-side checks verify ownership for the relevant lead, campaign, draft or conversation action. |
| Protected state-changing requests | Reduce accidental or unauthorised changes. | Supported account controls use authenticated request and token checks. |
| Worker claiming and row locks | Coordinate concurrent workers and editing actions. | Database transactions and row locks protect applicable claims and mutable message state. |
| Credit/action atomicity | Keep billing aligned with successfully persisted work. | Supported charged actions save their data and credit event in the same transaction. |
| Idempotent action references | Make retrying supported operations less error-prone. | Operation references prevent duplicate application of eligible credit and payment events. |
| Revision-aware editing | Avoid silently replacing a newer saved draft. | Supported ready, scheduled and redraft actions compare the submitted revision with current content. |
| Send-state edit locks | Protect messages already entering delivery. | Mutable-message checks reject sent, sending or otherwise locked states. |
| Generation context snapshots | Keep the factual basis of a draft available. | Saved snapshots retain seller, prospect and applicable conversation or sequence context. |
| Processing errors and retry state | Make interrupted work easier to recover and diagnose. | Worker stages record attempt counts, next-attempt times and error information. |
| Provider cost records | Support visibility into external processing costs. | Provider activity can record cost events for platform reporting. |
| Mailbox message identifiers | Support reliable thread linking and duplicate checks. | Outgoing and incoming records retain message identity and reference information. |
| JSON-driven workspace controls | Update actions through the web interface. | Supported browser controls call authenticated API endpoints and receive structured responses. |
Platform administration
Tools for Sales Lido’s operators; these are not customer-admin permissions.
| Feature | Productivity benefit | How it works |
|---|---|---|
| Administrator access control | Keep operator tools restricted to authorised staff. | Role checks gate the administration portal and its navigation. |
| User directory and search | Find the account that needs support. | The operator user list shows identity, status and registration details with search. |
| New-user visibility | Help operators support recent signups. | A new-user count, filter and badges identify accounts created in the recent signup window. |
| Account management actions | Resolve supported account problems. | User administration provides the implemented account status and management controls. |
| Account detail inspection | Give support the context needed to investigate. | Operator views expose the relevant user, lead, profile and campaign details. |
| Direct support conversations | Reply to a specific customer in context. | Administrators can open the user’s support-message thread. |
| Support message timestamps | Make conversations easier to follow. | Support messages include their recorded send times. |
| Support message deletion | Remove messages that no longer need to be retained. | Operator controls can delete individual support messages or clear a user thread. |
| Bulk support messaging | Communicate a platform notice across accounts. | The administration tools support sending a message to all users. |
| Newsletter composition | Prepare a platform update without editing code. | Operators can draft or paste newsletter content in the administration portal. |
| Newsletter delivery queue | Send platform communications in controlled batches. | Background delivery processes queued newsletter recipients and records delivery state. |
| Newsletter unsubscribe handling | Respect newsletter preferences. | The newsletter workflow includes its supported unsubscribe processing. |
| Credit pack administration | Adjust commercial pack settings centrally. | Operators can configure pack prices and included credit amounts. |
| Process-cost administration | Keep standard action pricing consistent across the platform. | Configured process costs are used by the supported credit-based workflows. |
| Central platform email settings | Manage platform notification identities from one place. | Supported contact, newsletter and password-reset sender settings are centrally configurable. |
| Credit usage graphs | Review platform consumption by period. | Operator reporting provides daily, weekly or monthly credit-usage views. |
| Provider cost reporting | Compare recorded third-party processing costs. | The administration area exposes supported provider cost events and totals. |
| Public website visitor statistics | Understand how the public pages are being used. | Aggregate reporting groups page views by date, page, source, device and browser. |
| Privacy-conscious aggregate visitor counts | Measure public page loads without building a visitor profile. | The visitor-statistics implementation avoids storing cookies, IP addresses or individual visit records and honours supported browser privacy signals. |
Mailbox features require a correctly configured sending account and inbox connection. Automated progress follows the selected mode, quality checks, available credits and sending rules. Platform administration tools are reserved for authorised Sales Lido operators.
Give Lido Ai the busywork.
Set your direction, choose how hands-on you want to be, and make more room for the customers who reply.