Beamreach AI Logo Beamreach AI

Yura Capability Map

Where your clients reach you, and where the work lands

Yura takes client messages from any channel, runs them through one pipeline, and writes the result into the systems your firm already uses. This page is the honest inventory — what is live today, what we are building now, and what we have not started.

Last updated 7 August 2026

Live — running in production today In development — being built now Roadmap — not started; client demand sets the order

Intake channels

How a client, a lead, or an event reaches Yura.

Email — Gmail & Google Workspace

Full inbox monitoring, attachments read and filed, replies drafted in-thread.

Website forms & chat widgets

A secured endpoint your site posts to. Works with any contact form, questionnaire, or chat tool.

WhatsApp — incoming messages

Official WhatsApp Business API, signature-verified. Messages become intake the same way email does.

Scheduled checks

Recurring runs on your schedule — weekly digests, deadline sweeps, government announcement monitoring.

Case status changes

A matter moving to retained, or any field changing, can start the next piece of work automatically.

One workflow finishing

Intake completing hands off to document review, which hands off to the next step. No human relay.

WhatsApp — outgoing replies

Drafting and approval work today; delivery back to the client is being wired up now.

WhatsApp — photos & documents

Clients photographing a passport in WhatsApp. In build, so it reaches document review like an email attachment.

O

Outlook & Microsoft 365 mailboxes

Email intake is Google-only today.

Voice calls & recordings

Designed for, deliberately unbuilt — we have not committed to a telephony vendor.

SMS

Same shape as WhatsApp; follows once a telephony vendor is chosen.

Facebook Messenger & Instagram DM

Shares WhatsApp's Meta plumbing, so it is a short build when a firm needs it.

Shared drive drop folders

Watching a Google Drive, OneDrive, or S3 folder and treating new files as intake.

Integrations

Where matters, documents, and notes are read from and written to.

Practice management

C

Clio

Contacts, matters, and notes through our published Clio connector. Deeper native support — reading a matter's history back into a client reply — is in build.

MyCase, PracticePanther, Smokeball

Practice management alternatives to Clio.

CRM & intake

H

HubSpot

Contacts and matter records created and updated from intake.

L

Lawmatics

Connector in development, following the same pattern as Clio.

S

Salesforce

For firms running a general-purpose CRM.

Documents & storage

G

Google Drive

Client folders created and documents filed under your own naming convention.

O

OneDrive & SharePoint

Document filing is Google Drive today.

iManage & NetDocuments

For firms with an existing document management system.

Email & workspace

M

Gmail

Replies drafted in the original thread for review, or sent directly where you have allowed it.

S

Google Sheets & Docs

Case tracker and document checklists — a working matter list without buying a CRM.

O

Outlook & Microsoft 365

Email is Google-only today.

Government sources

AIMA — Portugal

Public announcements monitored and cross-referenced against your client roster. Public pages only — never a client portal login.

USCIS case status

Blocked on a US-entity requirement for their developer programme, not on engineering.

Built in — nothing to connect

Document reading

Passports, certificates, and PDFs opened and checked for expiry dates, translation needs, and details that disagree between documents.

Public web research

Evidence gathering for extraordinary-ability and source-of-funds petitions, from public sources only.

n

Your own automation layer

Yura ships and updates workflows in an n8n instance deployed for your firm — the bridge to anything not yet native.

Why this list is shorter than you expected

Most vendors show you a wall of logos. Half of them are a checkbox someone clicked once. We would rather show you a short honest list and tell you what it costs to add the one you need.

Channels are interchangeable by design

Every channel is converted into one common shape before Yura reads it. Approvals, deduplication, and the audit trail are written once and apply to all of them. Adding a channel is a small piece of translation work, not a rebuild.

Grey moves when a client asks

The roadmap column is ordered by what firms actually ask for. Our Portugal workflows exist because Portuguese lawyers described a problem we had not thought of. Tell us which grey item blocks you.

It runs in your environment

Yura is deployed into infrastructure you control, alongside an automation layer we maintain for you. That is what makes "can you connect to our system?" a scoping conversation rather than a waiting list.

Need something that is not green yet?

Tell us which channel your clients actually use and which system your matters live in. If it is on this page in grey, we will tell you honestly what it takes to move it.