GetSellora Help Center

Get started with GetSellora

Follow these guides to create an AI Employee, add knowledge, enable tools and connect it with your customers.

Recommended launch sequence

Complete these steps in order so your AI Employee has everything it needs before going live.

01

Quick start

The basic path from creating an account to receiving the first verified response.

  1. 1

    Create a workspace or open an existing one.

  2. 2

    Create an AI Employee and choose its name, role and language.

  3. 3

    Configure behavior: identity, goals, rules, response style and restrictions.

  4. 4

    Add verified knowledge sources and wait for indexing to complete.

  5. 5

    Enable only the tools the employee actually needs.

  6. 6

    Verify responses in Test Chat before connecting the Website Widget.

Open section

02

AI Employees

Each AI Employee has an independent role, behavior, knowledge, tools and channels.

  1. 1

    The name helps your team identify the employee.

  2. 2

    The role defines its main function: support, sales, lead qualification or consulting.

  3. 3

    Goals explain which outcomes it should pursue during conversations.

  4. 4

    Rules and restrictions define what the employee may and may not do.

  5. 5

    Active status means the employee is ready to work in connected channels.

03

Knowledge Base

GetSellora uses the business information you add and successfully index.

  1. 1

    Website imports information from an accessible web page.

  2. 2

    PDF is useful for catalogs, guides, policies and presentations.

  3. 3

    Note lets you add internal information manually.

  4. 4

    FAQ stores precise question and answer pairs.

  5. 5

    Reindex a source after changing it and verify its status.

04

Tools

Tools allow an AI Employee to perform real actions instead of only generating responses.

  1. 1

    Knowledge Search finds relevant information in your sources.

  2. 2

    Lead Collection extracts contact details from customer messages and updates lead qualification in CRM.

  3. 3

    Calendar can create events after Google Calendar is connected.

  4. 4

    Human Handoff transfers the conversation to a person when the customer explicitly requests a human operator.

  5. 5

    Web Search, CRM Access and Custom API are also currently Coming soon.

  6. 6

    Lead Collection runs in real customer conversations with an attached contact; Test Chat does not create CRM contacts.

05

Channels

A channel determines where customers communicate with your AI Employee.

  1. 1

    Create a Website Widget for the required AI Employee.

  2. 2

    Configure its title, greeting, color and position.

  3. 3

    Add allowed domains so the widget only runs on your websites.

  4. 4

    Copy the installation code and add it before the closing body tag on your website.

  5. 5

    Open the website and complete a full test conversation.

06

GetSellora API

Connect websites, applications, CRMs and other services directly to an AI Employee.

  1. 1

    Open Channels → API, select an active AI Employee and create an API channel.

  2. 2

    Copy the complete secret key immediately after creation. GetSellora only displays a safe masked version afterwards.

  3. 3

    Send POST requests to https://getsellora.app/api/v1/messages with the Authorization: Bearer YOUR_API_KEY header.

  4. 4

    For safe retries, include a unique Idempotency-Key header of up to 128 characters. Repeating the same key and request body within 7 days returns the stored response without duplicating the message or consuming quota again.

  5. 5

    Do not reuse an Idempotency-Key with a different request body — the API returns HTTP 409.

  6. 6

    externalConversationId is required, accepts up to 200 characters and should consistently identify the conversation in your system.

  7. 7

    message is required and accepts up to 4000 characters.

  8. 8

    The optional contact object supports firstName, lastName, email, phone and company.

  9. 9

    Reusing the same externalConversationId continues the existing conversation and provides its previous history to the AI Employee.

  10. 10

    Status 201 means a new conversation was created, 200 means an existing conversation continued, and 202 means the conversation awaits an operator in Human mode.

  11. 11

    Each API channel accepts up to 30 requests per minute. Exceeding the limit returns HTTP 429 and Retry-After indicates how long to wait.

  12. 12

    Responses include X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset headers.

  13. 13

    Errors use JSON containing success, error.code, error.message and requestId.

  14. 14

    If a key is lost or exposed, generate a new one immediately. The old key is revoked automatically.

  15. 15

    Disconnecting an API channel revokes its key while preserving conversation and message history in GetSellora.

  16. 16

    Never expose an API key in browser JavaScript, Git, public repositories, logs or support messages.

07

Conversations and contacts

All conversations, messages, leads and next actions stay inside one workspace.

  1. 1

    Inbox displays new and active customer conversations.

  2. 2

    AI mode allows the AI Employee to answer automatically.

  3. 3

    Human mode pauses automatic replies and hands the conversation to an operator.

  4. 4

    A contact stores customer details, status, lead score, notes and history.

  5. 5

    Sales Pipeline shows the journey from a new lead to a customer.

08

Automations

A Workflow runs a sequence of actions after a defined business event.

  1. 1

    Choose a trigger such as contact created, message received or lead qualified.

  2. 2

    Add conditions when the automation should only run for specific data.

  3. 3

    Configure actions such as create task, change status, add tag, send email or run AI prompt.

  4. 4

    Save and test the Workflow manually before activation.

  5. 5

    Review execution history and failures.

09

Team and access

Workspace roles control who can view information and change configuration.

  1. 1

    Owner controls billing, team access and every setting.

  2. 2

    Admin can configure the workspace and AI Employees.

  3. 3

    Member works in available operational sections without changing configuration.

  4. 4

    Invite every teammate using their work email address.

  5. 5

    Do not share one account between multiple users.

Need help?

If something behaves unexpectedly, check the AI Employee configuration, knowledge status and enabled tools.