Reports, actions and permissions

Once connected, select Brixit in your AI app and describe what you need. Start with a profile check so you know which CRM account and company the assistant is using.

The expanded tools and report coverage below require Brixit 2.2.36. Update through your normal Brixit release process; no server configuration is needed. Existing connections keep their granted permissions. Reconnect and select CRM management access to enable the new editing tools.

Find records and prepare reports

Replace the sample names and dates below with your own. Only records your connected account can access are available.

Find the contact Sam Example and summarise their inquiries, notes and upcoming follow-ups. If there are multiple matches, let me choose one.

Find available two-bedroom listings matching my client’s requirements. Show the listing references and explain which requirements each matches.

How is our pipeline doing this month? Show the current stages and what changed.

Reports support agent activity, pipeline, listing performance, transactions and outreach, subject to your reporting permissions. Use ordinary periods such as “this month” or provide dates. The assistant resolves the time zone from CRM settings. Each report request can cover up to 366 days.

Search results default to 25 records per page and are capped at 50. MCP report tables default to 250 rows per table. When more rows exist, Brixit returns an explicit next tool call with the same filters. The assistant is instructed to fetch and combine the remaining pages needed for your request. You should not have to choose page numbers yourself. An AI app may still stop because of its own tool or context limits; it must then disclose the rows retrieved and the remaining coverage.

Pipeline reports distinguish inquiries created during the selected period from the current open pipeline across all dates. The current-stage breakdown reconciles to the current open total. For example, 132 currently open inquiries and one inquiry created this month can both be correct. Unassigned stages are labelled explicitly. Summary totals cover the permitted filtered dataset even when a detail table needs another page; missing detail pages do not make those totals partial. Data can change between requests, so a multi-page report is not a frozen snapshot.

Show a property

For an on-screen property presentation, ask “Show me BRX-106” with your listing reference. The property-card release adds photos, key facts, description, amenities, location, floor plans and tours. ChatGPT connections supporting app cards can display the interactive card; other clients receive the recorded details and photo links. External photos may open through a link, and unavailable images are identified. Owner identities and private employee contact details are excluded from this view.

Create PDF brochures and reports

Ask ChatGPT, Gemini or Claude to turn the Brixit information you can access into a downloadable document:

Make a PDF brochure for BRX-106 with its photos and key facts.

Compare the three properties we selected in a PDF, with prices first.

Turn this team report into a PDF with a short summary and the full table.

Brixit supplies the permitted records, report data and photo links. Your AI app creates the file using its own document tools when they are available in your session. This does not require Brixit write access or an additional Brixit server setup. Your AI app’s availability and usage limits still apply; connecting Brixit does not enable missing file tools.

Gemini supports native file generation and PDF downloads. Claude supports PDFs through code execution and file creation when that capability is enabled. ChatGPT uses its available document/code tools. An organization’s settings may limit file creation or access to property photos. If an image cannot be retrieved, the assistant should explain the omission instead of inventing a replacement or asking for broader CRM permissions.

The document should preserve the selected records, dates, currency, totals and any missing-data warnings. Photos must come from the listing and load successfully. A request for every row needs every page of the source data. Private owner details and internal notes do not belong in a client brochure unless specifically requested and permitted.

Open the actual PDF attachment and check it before sharing. If file creation is unavailable or fails, the assistant should explain that and offer the content as a draft. It should never invent a download link. Creating a PDF does not send it to anyone or save it back into Brixit. The CRM’s own report export interface remains available for its supported formats.

Add a note or schedule a follow-up

These actions require optional write access as well as your normal CRM permissions.

Find Sam Example. Show me the matching contact and ask for confirmation before adding the note: “Requested a two-bedroom apartment.”

Schedule a viewing for this contact on 1 November at 10 AM. Show me the details before saving.

Check the record, wording and time zone in the AI app’s approval prompt. Brixit enforces access permissions; the AI client controls the confirmation experience. Follow-ups may sync to your connected calendar through Brixit’s existing integration.

After approval, check the returned result and open the record in Brixit to confirm it saved. If a request times out, check for an existing note or follow-up before asking for another. The tools support duplicate-safe retries with the same request key; a new request may create another item.

Manage CRM records

CRM management access is a separate, optional permission in the Brixit consent screen. It enables creating contacts and inquiries, updating supported contact fields, moving an inquiry between stages in its pipeline, and editing existing notes and follow-ups. Your CRM role must also permit the action. Granting ordinary write access does not enable these tools.

Open Sam Example’s contact workspace. Summarise their inquiries, notes and follow-ups, then find matching properties for the inquiry I select.

Prepare a new buyer inquiry for the selected contact with a budget of 1.2–1.5 million. Use my account as the assigned agent and show me the details before saving.

Show the available stages for this inquiry’s pipeline, then move it to Viewing after I confirm the destination.

Mark the follow-up I selected as complete and update its remark to “Viewing completed; awaiting feedback.” Confirm the record and changes before saving.

The AI app controls its approval prompts. Check the proposed changes and the returned result. Existing CRM automations, notifications and calendar sync may run when a record changes.

Available tools

Read-only connections expose 16 tools. Write access adds two tools and CRM management adds six, for 24 tools when all three scopes are granted. Tool visibility does not override your CRM role or record access. There are no tools for bulk deletion, arbitrary database queries, sending email or unrestricted API access. A request outside these capabilities should be handled in the CRM itself.

Review or revoke access

Open User profile → AI connections in Brixit to see the connection’s access level, last use and reconnect date. Select Disconnect to stop future access. Previous AI conversations are retained according to the AI provider’s settings.

Your Brixit account must remain active with login enabled. Disabling or deactivating it blocks further MCP requests and connection refreshes, including for apps already connected.

For a permission failure, ask your administrator to check your CRM role rather than using someone else’s login. See troubleshooting.