Your first result

When an inquiry arrives, the outcome that matters is a reviewed decision with a recorded result, so you can see who confirmed what and what happened next. This guide follows one inquiry from a workspace you connected through the installation guide all the way to a reviewed action and its receipt, using the same screens your team will use each day.

You need: a connected installation with an owner account, and one inquiry you are willing to run end to end. Optional providers stay off until a workflow needs them, so you can finish this walkthrough with the database and authentication you already configured.

1. Confirm the workspace and enable what you need

Sign in at /admin and open Get started to follow your first saved opportunity. Invited workspace owners use their invitation; self-hosted owners complete Setup first. The checklist reads saved records, so progress survives reloads and stays available from the navigation. Review Modules for the optional capabilities your workflow needs. Core customer, pipeline and work capabilities remain available. Your workspace explains the membership and business context each screen expects before it shows data.

2. Bring the inquiry in

Open Contacts, then choose Website requests to review a submission or List import to import up to 500 pasted rows. The import checks for existing contacts before it saves, so you can inspect proposed matches and decide which records to save. Import a contact list covers the columns and review step, and Contacts explains where each saved row appears.

3. Give the inquiry somewhere to move

Open Pipeline and attach the person to an existing opportunity or create one with New opportunity. Every stage is a column on the board, and a move records a stage change against that opportunity, so the history travels with the record instead of sitting in an inbox. The pipeline board explains stages, dragging and the stage menu, while Pipeline explains how an opportunity relates to the contacts behind it.

4. Record a concrete next action

Open the relevant customer or opportunity and use its supported follow-up control to record the next task and date. For example, assign the agreed callback about the inquiry, then inspect the saved task in Work. This gives the team visible work without requiring an external send.

If AI is configured, you can instead request a supported task proposal for that exact record. Inspect it through Approvals, then confirm the result after execution. Creating an opportunity alone does not guarantee that an AI proposal will appear.

5. Read the recorded result

After you confirm an action, open Check an action result to read the receipt the system recorded for that specific effect. The receipt names the action, its source record and its terminal state, so you can tell a finished delivery from a queued or failed one without trusting a confirmation message.

6. Carry the lesson into the next inquiry

Add a reference document in Learning Inbox, then propose a correction worth reusing. After reviewing and approving it, run another relevant AI task and inspect which guidance it received. Get started checks the reference, linked task, approved correction and later context receipt separately, so you can see the next unfinished step.

Manual contact, opportunity and task work needs no AI or email credentials. Document indexing needs the work engine, and the final guidance check needs a configured model. The readiness section checks the same credential that AI execution uses, including the permitted self-hosted environment configuration. It distinguishes that configuration from a successful search, model call, scheduler run and completed follow-up. If the credential needs attention, manual tasks remain available while you repair the connection in Integrations.

What to check

• For an external reply, check the provider result and distinguish send acceptance from a recorded delivery event.
• Confirm the provider in Integrations, then check its successful execution receipt in Get started. Ask your platform operator to inspect Setup when installation work is required.
• Confirm the imported person appears once in Contacts and that the pipeline opportunity links to that same contact.
• Before importing a repeated file, inspect the existing batch and proposed matches so you do not create unintended duplicate records.
• If a step reports a problem, follow Troubleshooting by symptom before you retry.