Answer people questions from the handbook.

The same policy question lands in Slack every week. altspark lets your team's AI answer it from the handbook, with the page cited.

Book a demo
  • Answers cite the policy passage
  • Handbook, payroll and HR tools in one project
  • Onboarding runs as a workflow you approve

HR's repeat questions, each answered from the source.

  • What does the policy say about this?

    Anyone asks in Claude and gets the answer with the policy passage cited.

  • How many days do I have left?

    Ask your own balance from your own AI, on a server built to answer per person.

  • What did we agree in the offer letter?

    Offer letters and agreements read into a table: dates, terms and obligations you can ask about.

  • Onboard the next hire like the last one.

    A workflow runs the checklist across your tools, with an approval step wherever a person should decide.

  • Headcount across payroll and the HR system.

    Both kept current and joined in one question.

Put the handbook in the AI your team already uses.

  1. Connectors

    The handbook and the people tools, in one project.

    • Notion, Google and Microsoft through existing connectors.
    • Payroll and HR tools from their API docs.
    • Signed forms by email.
  2. Context layer

    Policies you can ask, with the passage cited.

    • Search by keyword and meaning together.
    • Offer letters and agreements read into a table.
    • Payroll and HR records joined.
  3. Workflows, Alerts & Surfaces

    Answers per person, and onboarding that runs.

    • Per-person limits, when you build for them.
    • Onboarding as a workflow.
    • A run can pause for a person.

Answer the policy question once, for everyone.

  • The whole company asks the handbook first

    Every plan has unlimited users, so everyone asks the handbook from their own AI before the question reaches HR.

  • Exit interviews you can ask

    Recorded exit interviews are transcribed, and you ask across them with the passages used.

  • Trial and contract dates, watched

    A saved question checks the agreements table each week and starts a reminder when a trial period or contract is about to end.

  • The next office onboards the same way

    Export the onboarding workflow with everything it needs, and install it for the next team or location.

  • One person's records, linked

    An employee's offer letter, payroll row and HR record answer as one person, with any guessed match put to you to confirm.

Start with the handbook.

Connect it and ask the question you answered most last week.

Security

People data, shared only as you set it.

  • Role-based access: salaries masked.
  • Writes back only where you allow it.
  • Credentials encrypted, every action logged.
  • SOC 2 Type 1 report.

Questions we hear

Yes. Roles decide which HR data stores and fields each person can see, so salaries or Social Security numbers can be hidden or partly masked for everyone outside HR. To show each employee only their own records, add a Check Access step that filters by who is signed in.

Yes, in your data stores. altspark flags fields that look like personal data, such as email, phone, Social Security number, date of birth, bank account or card number, by their names and their values, and suggests masking them. Once you accept, you choose for each role whether that field shows its real value, part of it, or nothing. Database connections are always read-only.

Only through a step you build for it, and you can require approval first. altspark never writes to databases, and every workflow run is logged.

Let the handbook answer the question HR answers every week.

Book a demo and bring your handbook.

Book a demo