Loading...
Loading...
Answers
How Huscribe answers whether the agent running today is the one you approved: the register, material changes, inspection reports, findings, access and release control.
Huscribe is an AI agent platform for sales and revenue teams. Six ready agents capture voice notes and meetings into the CRM, work inside WhatsApp, prepare meeting briefs, answer account questions with sources, flag stalled deals and run outreach. Teams describe further workflows in plain language and Huscribe builds them, inside the CRM and across connected tools. Ready agents connect to Salesforce, HubSpot, Zoho, Microsoft Dynamics 365 and Odoo. Workflow building inside the CRM covers Salesforce and Microsoft Dynamics 365 first, and registered agents acting on those platforms are inspected against what the business approved.
Yes. Your team describes the job in plain language: what should happen, which systems are involved and where a person approves. Huscribe builds the agent or workflow. Changes inside Salesforce or Dynamics 365 are tested in your sandbox and released by your team.
A sequence of steps carried by AI agents, with people approving at the points the business chooses. In Huscribe, a team describes the workflow in plain language, Huscribe builds it, and the running workflow is inspected against what was approved.
Yes. The Capture agent turns a voice note, a meeting or its own questions after a visit into drafted CRM changes, which the rep reviews and saves. Supported capture languages include English, Arabic and Hindi.
Huscribe writes down what each registered agent is approved to do, checks its behaviour against that approval on a schedule and when a material change is detected, and records the evidence in the customer’s Git repository. Inspection covers agents acting on Salesforce or Dynamics 365, whoever built them. A status reflects the latest inspection.
A SOC 2 Type II report, available under NDA, and ISO/IEC 27001:2022 certification. The security review states the covered entity, systems and scope.
Your people write down what the agent may and may not do, and sign it: outcomes, prohibited actions, escalations and limits. The approval is kept by version, and every check is compiled from it, so a check always traces back to something a person signed.
One row per agent: who owns it, as a named business owner and a named platform owner, what it was approved to do by version, whether it still does that, what changed last and its source, and where the evidence is. Nothing is green by default. An agent nobody has inspected shows as not inspected.
A model swapped by the vendor, a prompt edited, a permission widened, a configuration change, a knowledge article edited, or a flow changed upstream. Checks run on a schedule and again on each of these, because most of them leave no deployment record.
Salesforce and Dynamics 365 agents first, whoever built them: agents Huscribe builds for you, agents your team or a vendor built, and workflows that hand off between the two.
The failure becomes a finding: the check, the evidence quoted from the report, the proposed cause, and the smallest change that would pass. The agent's owner decides, your team ships it, and Huscribe checks again.
Huscribe takes it to a release candidate in your sandbox, with the approval attached and the checks written from it. Your team releases it. Huscribe never deploys, and the build never happens in production.
Every answer in the register links to its report. The approval, the checks, the reports and the release candidate go into a repository you control, readable without Huscribe.
Huscribe’s six ready agents connect to Salesforce, HubSpot, Zoho, Microsoft Dynamics 365 and Odoo; coverage varies by agent and is confirmed at setup. Workflow building inside the CRM and agent inspection cover Salesforce and Microsoft Dynamics 365 first.
Yes. Six agents are available on their own: the Capture agent, the WhatsApp agent, the Context agent, the Meeting-brief agent, the Deal intelligence agent and the Outreach agents. Each enters your register with its approval attached and is inspected on the same schedule as anything else you run. They connect to Salesforce, HubSpot, Zoho, Dynamics 365 and Odoo.
CRM admin eats a serious share of every rep's week: industry research puts non-selling activities at 72% of it (Salesforce, State of Sales). More often, the logging just doesn't get done. With voice, they can update their CRM on the commute, walking out of a meeting, right when the memory is fresh. The data actually gets logged, and your pipeline stays clean.
Huscribe supports English, Arabic, Hindi, and a growing list of languages. Voice commands are transcribed as you speak, and you review the proposed update before it is committed.
Review before commit applies on every capture route except meeting transcriptions and summaries, which commit automatically and can be undone afterwards. Everywhere else, Huscribe shows you exactly what it's about to update and waits for you to review, edit, or approve. You can automate certain repetitive tasks, but by default, Huscribe asks first.
Standard fields like deal stage, close date and contact info, and your custom fields too: Huscribe reads your CRM schema and maps voice input to the right fields. You review the proposed update before it is committed.
Open Huscribe on your phone and let it listen. It captures the conversation through your device microphone, transcribes it in real-time, and extracts the CRM action items once the meeting ends.
Yes. Each rep gets their own Huscribe account, and all updates sync to your shared CRM instance.
You review proposed updates before they are committed, on every capture route except meeting transcriptions and summaries, which commit automatically and can be undone afterwards. Extracted information carries its source and date, so a reviewer can see where anything came from.
Recordings and their structured output (transcripts, CRM updates, and action items) are handled under documented retention and deletion controls. Deletion is handled under the published retention and deletion policy. Data is encrypted in transit and at rest.
Huscribe uses leading speech recognition models, and it learns the terms your team uses. You review proposed updates before they are committed, on every capture route except meeting transcriptions and summaries, which commit automatically and can be undone afterwards.
Yes. Data is encrypted with TLS 1.3 in transit and AES-256 at rest. Huscribe holds a SOC 2 Type II report covering all Huscribe services, available for review under NDA, and is ISO/IEC 27001:2022 certified. Enterprise features include audit logs and role-based access control.
Yes. Everything Huscribe does for a rep can be done from the phone. The Huscribe app on iOS and Android takes a voice note between visits, on the commute or straight after a meeting, and turns it into CRM-ready records: deals updated, calls logged, contacts created, follow-ups scheduled. It is built for field sales, and for anyone who does not have the time to open the system and type the update in.
Yes. That is the Capture agent. A rep records a voice note in the app, or sends it on WhatsApp, and Huscribe turns it into the records and follow-ups, with the email and calendar context attached. Nobody has to open the CRM. The rep reviews what Huscribe drafted and approves it from the phone.
Yes. The WhatsApp agent drafts CRM updates and customer follow-ups inside the conversation. Reps review each record before it is saved and each follow-up before it is sent.
About 2 minutes to connect your CRM account, and you can start using voice commands to update your CRM right away. Scoped workflow changes follow their own preflight and build timeline, agreed before the work starts.
Yes. Huscribe lets you create custom voice commands and shortcuts for your most common CRM tasks. You can also set up industry-specific terminology and phrases.
WhatsApp messages, Gmail and Outlook emails, call transcripts from Zoom and Google Meet, plus shared files and documents.
Context from connected channels syncs to your CRM, following the workflow you configure. The timeline enriches your existing CRM records so everything lives in one place, not a separate tool.
Yes. Ask things like "who mentioned budget concerns this month?" or "which deals have gone quiet?" and Huscribe searches across every client interaction to surface the answer.
By default, context is shared across the team so managers and colleagues can see the full client picture. Permissions are configurable by the team's admin.
Nothing is lost. Every detail captured by that rep stays in Huscribe and remains accessible to the team. When a new rep takes over the account, they get the full timeline from day one.
Yes. Proposals, contracts, pricing sheets, and documents shared over email or WhatsApp are all indexed and attached to the client timeline.
From what's actually happening in conversations. Huscribe analyses call transcripts, WhatsApp messages, emails, and meeting notes to score each deal based on engagement, sentiment, commitment follow-through, and recency of contact. It's not a number someone typed into a field. It's what the data actually says.
Yes. You choose which metrics matter: deal health, team activity, pipeline velocity, stalled deals, overdue follow-ups.
Yes. Reports can be shared in formats like Excel, PDF, and as a shareable Huscribe link with specific team members, managers, or leadership. The team admin controls who sees what.
That's exactly when it's most useful. Huscribe doesn't rely just on structured CRM data. It generates intelligence from actual conversations: WhatsApp threads, call transcripts, and emails.
Yes. Managers and leaders can see how many conversations each rep is having, how quickly they follow up, which deals they're progressing, and where they're dropping the ball. No micromanaging needed.
Yes. If a deal goes quiet, a client's sentiment shifts, or a commitment was missed, Huscribe flags it via WhatsApp or email.
In real-time. Every new conversation, email, or meeting updates the context and intelligence automatically. By the time you need it, it's already there.
Nothing. We take one workflow and look at whether your systems still fit the way that work actually runs, and whether the gap can be measured. It works best when you have a sandbox, a real release process and someone who can approve a change. It starts with your workflow rather than a product tour, and if it does not qualify we say so on the call.
We do not change your existing agents, automations or custom code, we do not make destructive changes to your configuration, and we do not deploy to production. General administration and technical debt cleanup are not what this is for.
Fixed price, agreed before we start, scoped to one workflow. No open-ended hours.
Production discovery uses a dedicated identity you approve, through a service restricted to retrieval, scoped to the workflow we agreed. Build and testing use a separate sandbox connection.
No. Huscribe builds and tests workflow changes in your sandbox; your team approves the plan and the tested change and decides when to release. This boundary is about deploying workflow changes. An approved running agent still performs the record actions your people approved.
Project deliverables and usage rights are set out in the agreement. The source, tests, documentation, deployment manifest and Release Candidate go into a repository you control. Huscribe keeps its own platform and reusable tooling. Any continuing dependency on Huscribe is disclosed before you approve the build.
Campaign Copilot is our working Salesforce reference implementation. It plans first, waits for a person to approve, uses no hidden service account, is tested not to duplicate, and prepares the campaign for your marketing team to send.
The build is scoped in weeks. Total elapsed time depends on your release calendar, which is why we agree the release slot before we begin rather than hoping for one at the end.
We record the exact version that went live and observe the agreed metric over the window set at baseline. Where a delivered component depends on Huscribe hosted services, that dependency and its support terms are stated in the agreement before you approve the build. Your team owns the release and the rollback path.
Often you should, and the preflight will say so when the answer is configuration you already own. It gets harder when the change needs designing, testing, permission and dependency analysis, and evidence that it works, on top of everything your admin already carries. We do that for one workflow and hand it to them.
For a broad programme, maybe you should, and good ones diagnose as well as build. Huscribe is deliberately narrower: one measurable workflow, compared against live evidence, the same artifact set every time, two approval gates, a fixed price.
Use them. We do, where they are the right answer. Native tools are good at generating a change. Huscribe adds what sits around it: the comparison that picks the workflow, the call on whether an agent is even needed, the release evidence, and the observed result.
Email us, or name one agent and Huscribe comes back with what it was approved to do and whether it still does.