/* Mesh website — FAQ content.
   FAQ_HOME: the 5 conversion-focused questions for the homepage block.
   FAQ_GROUPS: the full, category-grouped set for the dedicated /faq page.
   Answers are 40–60 words, confident and specific. Verb-first questions keep
   the verb-first pattern; capitalization is sentence case throughout. */

window.FAQ_HOME = [
  {
    q: 'Are you SOC 2 compliant, and where is our data stored?',
    a: 'Yes, Mesh is SOC 2 Type II certified, audited annually by an independent third party. Your data is encrypted in transit and at rest and hosted in US-based AWS regions. Access is least-privilege by default, and we never train shared models on your financial data. Regional data residency is available on enterprise plans.'
  },
  {
    q: 'Do we still get human review before anything posts to the ERP?',
    a: 'Always. Mesh never posts to your ERP on its own. Every accrual it drafts lands in a review queue where your team approves, edits, or rejects it before anything syncs. You remain as the system of record, Mesh handles gathering, calculation, and documentation, and your controllers keep the final sign-off.'
  },
  {
    q: 'We tried building this internally, why is Mesh different?',
    a: 'Most internal builds stall on maintenance, not the first version. Mesh maintains the connectors, judgment logic, and audit trail as your vendors, ERP, and team change, so it does not rot the moment its author leaves. You get versioned rules, exception flagging, and full lineage out of the box, not a brittle script to babysit.'
  },
  {
    q: 'Can we run a lightweight proof of concept first?',
    a: 'Yes. Most teams start with a focused proof of concept on one entity or a handful of vendors, using recent close workbook(s) you already trust. It takes days, not months: we connect read-only, replay the period, and you compare Mesh\u2019s output against your own. No rip-and-replace required to see the value.'
  },
  {
    q: 'What does implementation actually require from us?',
    a: 'We connect to your ERP and procurement systems (i.e. Coupa, Zip) with read-only access, then sit with your team to encode your existing accrual logic once. Most teams run their first Mesh-assisted close within weeks, resulting in minimal disruption to your close cycles.'
  },
];

window.FAQ_GROUPS = [
  {
    cat: 'Is Mesh different from what we\u2019ve tried?',
    items: [
      {
        q: 'We tried building this internally, why is Mesh different?',
        a: 'Most internal builds stall on maintenance, not the first version. Mesh maintains the connectors, judgment logic, and audit trail as your vendors, ERP, and team change, so it does not rot the moment its author leaves. You get versioned rules, exception flagging, and full lineage out of the box, not a brittle script to babysit.'
      },
      {
        q: 'How is Mesh different from a generic automation or RPA tool?',
        a: 'RPA replays clicks and breaks the moment a screen changes. Mesh understands accrual accounting: it reads source documents, applies the judgment your team encodes, and explains every figure. Instead of automating a fragile workflow, it produces auditable journal entries with assumptions and lineage attached, work an auditor can actually follow.'
      },
      {
        q: 'Does Mesh replace our accounting team?',
        a: 'No. Mesh removes the manual gathering, tie-outs, and copy-paste that consume close week, so your team spends its time on judgment and review instead. Controllers stay in control, approving entries, setting policy, and handling exceptions. Mesh is leverage for the people you have, not a replacement for them.'
      },
    ],
  },
  {
    cat: 'Can we trust you with our data?',
    items: [
      {
        q: 'Are you SOC 2 compliant, and where is our data stored?',
        a: 'Yes, Mesh is SOC 2 Type II certified, audited annually by an independent third party. Your data is encrypted in transit and at rest and hosted in US-based AWS regions. Access is least-privilege by default, and we never train shared models on your financial data. Regional data residency is available on enterprise plans.'
      },
      {
        q: 'Do you train AI models on our financial data?',
        a: 'No. Your financial data is never used to train shared or third-party models. Mesh applies your encoded logic within your isolated tenant, and any model use runs under strict data-processing terms with no retention for training. Your numbers stay yours, used only to do your work.'
      },
      {
        q: 'Who on our team can see and access what?',
        a: 'You control access with role-based permissions and SSO. Reviewers, approvers, and admins each see only what their role requires, and every view or change is logged. You can scope access by entity or workflow, so a contractor or junior analyst never sees more of your books than they should.'
      },
      {
        q: 'What happens to our data if we leave?',
        a: 'It stays portable. You can export your entries, assumptions, and full audit trail at any time, in formats your ERP and auditors accept. On offboarding we delete your data on a defined schedule and provide written confirmation. There is no lock-in holding your close hostage.'
      },
    ],
  },
  {
    cat: 'Connecting Mesh to our systems',
    items: [
      {
        q: 'Which ERPs and systems does Mesh connect to?',
        a: 'Mesh connects to major ERPs including NetSuite, Sage Intacct, and QuickBooks, plus procurement tools, AP inboxes, contract repositories, and data warehouses. It also reads context from Slack, Teams, and email. If a system holds vendor signal, we likely already integrate, and we add connectors based on customer demand.'
      },
      {
        q: 'How long does it take to connect our systems?',
        a: 'Usually days. Core ERP and source-system connections use standard authentication and read-only access, so there is no heavy IT project. We handle mapping with your team, validate against a recent close, and confirm the numbers tie out before you rely on anything. Most connections are live in the first week.'
      },
      {
        q: 'Do you need write access to our ERP?',
        a: 'Only when you choose to enable posting, and only after human approval. Mesh runs read-only by default, it gathers and drafts without touching your books. If you turn on write-back, every entry still passes through your review queue first, and you can revoke posting access at any time.'
      },
      {
        q: 'Can Mesh pull context from Slack, Teams, and email?',
        a: 'Yes. Mesh reads the messages, threads, and shared inboxes where accrual context actually lives, a vendor confirming usage, a PO discussed in Slack, an invoice forwarded over email. It links that evidence to the relevant entry, so the reasoning behind a number is captured instead of lost in someone\u2019s DMs.'
      },
    ],
  },
  {
    cat: 'Handling our real data',
    items: [
      {
        q: 'How does Mesh handle messy or inconsistent vendor data?',
        a: 'That is the normal case, not the exception. Mesh reconciles signals across documents, systems, and messages, normalizes vendor names and amounts, and flags what it cannot confidently resolve. Instead of forcing clean inputs, it surfaces the gaps, missing statements, mismatched totals, so your team fixes the few things that genuinely need a human.'
      },
      {
        q: 'What happens when a vendor or contract changes?',
        a: 'Mesh notices. Because it watches your source systems continuously, a new contract term, changed PO, or shifted billing cadence shows up as a flagged change rather than a silent error. Your encoded logic adapts going forward, and the change is documented in the audit trail with the evidence that triggered it.'
      },
      {
        q: 'Can Mesh handle multiple entities and currencies?',
        a: 'Yes. Mesh supports multi-entity structures and multi-currency vendors, applying the right logic and rates per entity while keeping a consolidated view. Intercompany and per-entity rules are encoded once and applied consistently, so a complex org chart does not mean a different manual process for every subsidiary.'
      },
    ],
  },
  {
    cat: 'How it posts to our books',
    items: [
      {
        q: 'Do we still get human review before anything posts to the ERP?',
        a: 'Always. Mesh never posts to your ERP on its own. Every accrual it drafts lands in a review queue where your team approves, edits, or rejects it before anything syncs. You remain as the system of record, Mesh handles gathering, calculation, and documentation, and your controllers keep the final sign-off.'
      },
      {
        q: 'How does Mesh actually post journal entries?',
        a: 'Once you approve an entry, Mesh writes it to your ERP through the same standard integration your team would use, with the assumptions and supporting evidence attached. You choose whether to post automatically on approval or stage entries for a batch. Either way, nothing reaches your books without sign-off.'
      },
      {
        q: 'What happens when Mesh isn\u2019t sure about an accrual?',
        a: 'It asks instead of guessing. When an assumption is missing or a change looks material, Mesh flags the item, explains why, and routes it for human judgment rather than posting a number it cannot defend. Confident, well-supported entries clear automatically; the genuinely ambiguous ones get your attention.'
      },
    ],
  },
  {
    cat: 'Standing up to audit',
    items: [
      {
        q: 'How does Mesh hold up in an audit?',
        a: 'Audits become a query, not a fire drill. Every figure carries a complete, time-stamped record of its sources, assumptions, calculations, and approvals. When an auditor asks where a number came from, you click it and show the lineage, no reconstructing logic from memory or hunting through old spreadsheet tabs.'
      },
      {
        q: 'Can auditors trace where every number came from?',
        a: 'Yes. Each entry links back to the exact documents, messages, and system records behind it, plus the rule version applied and who approved it. The trail is immutable and exportable, so auditors can follow any figure end to end without waiting on your team to assemble support after the fact.'
      },
      {
        q: 'Does Mesh support SOX controls and documentation?',
        a: 'Yes. Mesh enforces segregation of duties through role-based approvals, logs every action immutably, and documents the control automatically as work happens. The consistent, versioned logic and complete evidence trail give your SOX program the repeatability and documentation it needs, without your team maintaining a separate binder of screenshots.'
      },
    ],
  },
  {
    cat: 'Trying Mesh',
    items: [
      {
        q: 'Can we run a lightweight proof of concept first?',
        a: 'Yes. Most teams start with a focused proof of concept on one entity or a handful of vendors, using recent close workbook(s) you already trust. It takes days, not months: we connect read-only, replay the period, and you compare Mesh\u2019s output against your own. No rip-and-replace required to see the value.'
      },
      {
        q: 'What does implementation actually require from us?',
        a: 'We connect to your ERP and procurement systems (i.e. Coupa, Zip) with read-only access, then sit with your team to encode your existing accrual logic once. Most teams run their first Mesh-assisted close within weeks, resulting in minimal disruption to your close cycles.'
      },
      {
        q: 'How is Mesh priced?',
        a: 'Pricing scales with the work Mesh handles for you, entities, volume, and the systems you connect, not per seat, so adding reviewers never costs more. After a short scoping call we give you a flat, predictable annual number. Most teams find it well below the cost of the close days it returns.'
      },
    ],
  },
];