{
  "version": 4,
  "kind": "lists",
  "app": "Experto",
  "exportedAt": "2026-10-01T04:09:18.102Z",
  "settings": {
    "theme": "light",
    "language": "en-US",
    "timeZone": "America/Sao_Paulo",
    "selectedListId": "comece",
    "activeTab": "lists",
    "lastSyncAt": null,
    "seededMessagesAt": null
  },
  "profile": null,
  "lists": [
    {
      "id": "comece",
      "name": "Start here",
      "color": "#4f7fe8",
      "position": 0,
      "kind": "account",
      "createdAt": "2026-10-01T04:09:18.102Z",
      "updatedAt": "2026-10-01T04:09:18.102Z",
      "deletedAt": null
    },
    {
      "id": "recebidos",
      "name": "Incoming requests",
      "color": "#7a8aa0",
      "position": 1,
      "kind": "account",
      "nextListId": "execucao",
      "nextEstimate": {
        "amount": 3,
        "unit": "business_days"
      },
      "createdAt": "2026-10-01T04:09:18.102Z",
      "updatedAt": "2026-10-01T04:09:18.102Z",
      "deletedAt": null
    },
    {
      "id": "aprovacao",
      "name": "Leadership approval",
      "color": "#3aa2e6",
      "position": 2,
      "kind": "account",
      "nextListId": "execucao",
      "nextEstimate": {
        "amount": 3,
        "unit": "business_days"
      },
      "createdAt": "2026-10-01T04:09:18.102Z",
      "updatedAt": "2026-10-01T04:09:18.102Z",
      "deletedAt": null
    },
    {
      "id": "execucao",
      "name": "In progress",
      "color": "#f2b233",
      "position": 3,
      "kind": "account",
      "nextListId": "entrega",
      "nextEstimate": {
        "amount": 2,
        "unit": "business_days"
      },
      "createdAt": "2026-10-01T04:09:18.102Z",
      "updatedAt": "2026-10-01T04:09:18.102Z",
      "deletedAt": null
    },
    {
      "id": "entrega",
      "name": "Requester sign-off",
      "color": "#5fc266",
      "position": 4,
      "kind": "account",
      "createdAt": "2026-10-01T04:09:18.102Z",
      "updatedAt": "2026-10-01T04:09:18.102Z",
      "deletedAt": null
    },
    {
      "id": "recusados",
      "name": "Declined",
      "color": "#f26d6d",
      "position": 5,
      "kind": "account",
      "createdAt": "2026-10-01T04:09:18.102Z",
      "updatedAt": "2026-10-01T04:09:18.102Z",
      "deletedAt": null
    }
  ],
  "items": [
    {
      "id": "item-1",
      "listId": "comece",
      "title": "1. Turn on sub-accounts as Areas",
      "description": "**Why:** each department that handles requests becomes a sub-account. That's what says who each request is for and lets each department filter its own queue.\n\n**How to do it:**\n\n1. Open **Administration › Account**.\n2. Switch on **Turn on sub-accounts**.\n3. In **Call them**, choose **Areas** (or **Departments**, or **Sectors**, if that's what your company calls them).\n\n**Done when:** **Manage areas** shows up on the account page.",
      "dueAt": null,
      "durationMinutes": null,
      "startAt": null,
      "startMode": "auto",
      "done": false,
      "completedAt": null,
      "position": 0,
      "createdAt": "2026-10-01T04:09:18.102Z",
      "updatedAt": "2026-10-01T04:09:18.102Z",
      "deletedAt": null
    },
    {
      "id": "item-2",
      "listId": "comece",
      "title": "2. Add the departments that handle requests",
      "description": "**How to do it:** in **Administration › Account › Manage areas**, create a **New area** for each department that gets requests, like Finance, HR, IT, Legal, Purchasing and Marketing. Use the short name everyone already uses: that's what goes after the `#` in a request.\n\n**What comes with it:** each area you create automatically gets its own list, **Lista - {area name}** (you can rename it), good for whatever is internal to that department.\n\n**Heads up:** this list starts open to the area, which means anyone invited as a guest of that area sees what's in it. To keep it within the team, open the list settings and set **Areas who see it** to **None**.\n\n**Done when:** every department that handles requests is added.",
      "dueAt": null,
      "durationMinutes": null,
      "startAt": null,
      "startMode": "auto",
      "done": false,
      "completedAt": null,
      "position": 1,
      "createdAt": "2026-10-01T04:09:18.102Z",
      "updatedAt": "2026-10-01T04:09:18.102Z",
      "deletedAt": null
    },
    {
      "id": "item-3",
      "listId": "comece",
      "title": "3. Pick the point people, turn on the key date and check business hours",
      "description": "**Point person:** in each department, agree on who triages new requests every business day. It can be the manager or someone on the team, and it's worth having a backup for vacations.\n\n**Key date:** in **Administration › Account**, turn on **Use key date**. Use the key date as the day the requester needs the delivery. It stays fixed while the request moves through the lists, separate from each stage's deadline.\n\n**Business hours:** on the same page, under **Business days and hours**, check the company's days and hours. The deadline on each handoff counts in business time from them.\n\n**Done when:** every department has its point person, the key date is on and your business hours are right.",
      "dueAt": null,
      "durationMinutes": null,
      "startAt": null,
      "startMode": "auto",
      "done": false,
      "completedAt": null,
      "position": 2,
      "createdAt": "2026-10-01T04:09:18.102Z",
      "updatedAt": "2026-10-01T04:09:18.102Z",
      "deletedAt": null
    },
    {
      "id": "item-4",
      "listId": "comece",
      "title": "4. Choose who's in each list",
      "description": "**Why:** the template's lists arrive as **Admins only**. The company only sees them after this step.\n\n**How to do it**, in each list's settings, under **Who’s in**:\n\n- **Incoming requests:** **Specific people**, with the point people and the managers. Every new request notifies them, and the rest of the company asks through the form (step 6). If you'd rather have everyone open requests straight from **New item**, use **Everyone in the account**: then no one gets a new-request notification, and the point person checks the list every day.\n- **Leadership approval:** **Specific people**, with the directors who approve and the point people, who move requests there. Every request that arrives notifies them.\n- **In progress:** **Everyone in the account**, or only the people in the departments that handle requests.\n- **Requester sign-off** and **Declined:** **Everyone in the account**, so the requester can check and complete.\n\n**Done when:** everyone sees the lists they work in.",
      "dueAt": null,
      "durationMinutes": null,
      "startAt": null,
      "startMode": "auto",
      "done": false,
      "completedAt": null,
      "position": 3,
      "createdAt": "2026-10-01T04:09:18.102Z",
      "updatedAt": "2026-10-01T04:09:18.102Z",
      "deletedAt": null
    },
    {
      "id": "item-5",
      "listId": "comece",
      "title": "5. Invite directors who only approve (optional)",
      "description": "**Who for:** a director who only approves and doesn't handle requests can join as a guest, without taking up a seat.\n\n**How to do it:**\n\n1. In the **Leadership approval** list settings, under **Areas who see it**, choose **All areas**. The other lists stay on **None**.\n2. On each area's profile, in **Administration › Account › Manage areas**, invite its director by email or link.\n\n**How it works for a guest director:** they only see their department's requests waiting for approval, with the title, description, deadlines and attachments. Completing means approving, and the request moves on to In progress. It works on the web and in the iPhone app.\n\n**To decline:** a guest can only complete. If the director declines, they let the point person know, who moves the request to **Declined** with the reason. A director who needs to decline in the app joins as an account member.\n\n**Done when:** every guest director has accepted the invite, or every director is in Who’s in for Leadership approval.",
      "dueAt": null,
      "durationMinutes": null,
      "startAt": null,
      "startMode": "auto",
      "done": false,
      "completedAt": null,
      "position": 4,
      "createdAt": "2026-10-01T04:09:18.102Z",
      "updatedAt": "2026-10-01T04:09:18.102Z",
      "deletedAt": null
    },
    {
      "id": "item-6",
      "listId": "comece",
      "title": "6. Turn on the request form",
      "description": "**How to do it:** in the **Incoming requests** settings, under **Receive from another tool**, click **Turn on** and use **This list's address** in your company's request form.\n\n**Suggested fields**, with these names so Experto recognizes them on its own:\n\n- **Subject:** becomes the request's title.\n- **Description:** what's needed, in as much detail as possible.\n- **Key date:** when the requester needs it. It becomes the request's key date.\n- **Area:** the department that will handle it, with the name exactly as set up. On the first submission, the screen asks which field is the area.\n- **Requested by** and **Email:** who's asking. Fields Experto doesn't know go to the bottom of the description.\n\nAvoid a field called just **Name**: Experto may read it as the title.\n\n**Done when:** a test request sent through the form shows up in Incoming requests with the area tagged.",
      "dueAt": null,
      "durationMinutes": null,
      "startAt": null,
      "startMode": "auto",
      "done": false,
      "completedAt": null,
      "position": 5,
      "createdAt": "2026-10-01T04:09:18.102Z",
      "updatedAt": "2026-10-01T04:09:18.102Z",
      "deletedAt": null
    },
    {
      "id": "item-7",
      "listId": "comece",
      "title": "7. Agree on the workflow rules with the company",
      "description": "- **Same naming pattern:** `[Type] Subject · Requester`, for example `[Purchase] Laptop for the new designer · Ana`. With the requester's name in the title, they find their request with search.\n- **To open a request from New item,** type `#IT` to tag the area and `@Incoming requests` to send it to the right list, from wherever you are. Both leave the title.\n- **Triage within 1 business day.** The point person checks the request is complete and completes it: the request moves to In progress with a 3-business-day deadline. If the key date calls for a different deadline, adjust **Due by** there.\n- **Needs approval** (it costs money, falls outside policy, touches access)? Use **Move to… › Leadership approval** and set a deadline.\n- **Missing information?** Write in the description what's missing and talk to the requester. The request stays in Incoming requests until it's complete.\n- **Won't be done?** Use **Move to… › Declined**, with the reason in the description, and complete it.\n- **Whoever does it gives it a Pull.** The request goes into that person's checklist for the day, and everyone sees who has it. Couldn't get to it? Push sends it back.\n- **Delivered?** Complete it: the request moves to Requester sign-off, with 2 business days for the requester to check and complete it. No answer by then? The point person checks and completes it.",
      "dueAt": null,
      "durationMinutes": null,
      "startAt": null,
      "startMode": "auto",
      "done": false,
      "completedAt": null,
      "position": 6,
      "createdAt": "2026-10-01T04:09:18.102Z",
      "updatedAt": "2026-10-01T04:09:18.102Z",
      "deletedAt": null
    },
    {
      "id": "item-8",
      "listId": "comece",
      "title": "8. Take the sample requests through the workflow",
      "description": "**Incoming requests** has two sample requests:\n\n1. Tag a test area on each, in the **Area** field.\n2. On the purchase request, finish triage and watch it arrive in **In progress** with a deadline.\n3. Give it a **Pull**, see it in your checklist for the day and complete it: it lands in **Requester sign-off**.\n4. Complete it in Requester sign-off, as if you were the requester.\n5. On the access request, use **Move to… › Leadership approval** and approve it by completing it. It moves on to In progress.\n6. Finally, try **Move to… › Declined** with any request.\n\n**Done when:** both samples are completed in Requester sign-off.",
      "dueAt": null,
      "durationMinutes": null,
      "startAt": null,
      "startMode": "auto",
      "done": false,
      "completedAt": null,
      "position": 7,
      "createdAt": "2026-10-01T04:09:18.102Z",
      "updatedAt": "2026-10-01T04:09:18.102Z",
      "deletedAt": null
    },
    {
      "id": "item-9",
      "listId": "comece",
      "title": "9. Adjust deadlines to each department's pace",
      "description": "Each list gives the request a deadline when it moves to the next one (list settings › **Connected list** › **Estimate**):\n\n| When it arrives in | Deadline |\n|---|---|\n| In progress (from Incoming requests) | 3 business days |\n| In progress (from Leadership approval) | 3 business days |\n| Requester sign-off | 2 business days |\n| Leadership approval | set by whoever moves it |\n\nA request bigger or more urgent than usual? Change **Due by** once it's in In progress. The key date shows when the requester needs it.\n\n**Done when:** the deadlines reflect what each department can deliver.",
      "dueAt": null,
      "durationMinutes": null,
      "startAt": null,
      "startMode": "auto",
      "done": false,
      "completedAt": null,
      "position": 8,
      "createdAt": "2026-10-01T04:09:18.102Z",
      "updatedAt": "2026-10-01T04:09:18.102Z",
      "deletedAt": null
    },
    {
      "id": "item-10",
      "listId": "comece",
      "title": "10. Connect your AI agent (optional)",
      "description": "**How to turn it on:** in **Administration › AI agents**, turn on **Allow AI connections** and choose whether the AI can only read or also edit. Then each person connects their own agent (Claude, ChatGPT or any other MCP-compatible app) at getexperto.com/app/mcp. The AI only sees what that person sees.\n\n**Account context for the AI** (on the same screen): write down the departments, what each one handles, the point person and the request naming pattern (`[Type] Subject · Requester`).\n\n**Sample requests:**\n\n- \"Turn the action items from this meeting into requests in Incoming requests, each with the right area and the key date.\" (up to 50 items per request)\n- \"Which Finance requests are overdue?\"\n- \"What has been waiting for leadership approval for more than 2 days?\"\n\nThe AI never deletes anything.",
      "dueAt": null,
      "durationMinutes": null,
      "startAt": null,
      "startMode": "auto",
      "done": false,
      "completedAt": null,
      "position": 9,
      "createdAt": "2026-10-01T04:09:18.102Z",
      "updatedAt": "2026-10-01T04:09:18.102Z",
      "deletedAt": null
    },
    {
      "id": "item-11",
      "listId": "recebidos",
      "title": "[Purchase] Sample · Laptop for the new designer · Ana",
      "description": "This is a sample request. Take it through the workflow following step **8** of **Start here**.\n\n**Request template** (the form and New item can follow this outline):\n\n- **What's needed:** a laptop for the designer who starts on the 3rd, with the design apps installed.\n- **By when:** on the key date.\n- **Why:** the new hire starts without equipment.\n- **Requested by:** Ana, from Marketing.\n- **Attachments:** the minimum specs, if any.\n\n**Triage (point person):**\n\n1. Is the request complete? If something is missing, write it here and talk to the requester.\n2. Does it cost money or fall outside policy? Use **Move to… › Leadership approval**.\n3. All good? Complete it. The request moves to In progress with a 3-business-day deadline, which you adjust there if the key date calls for it.",
      "dueAt": null,
      "durationMinutes": null,
      "startAt": null,
      "startMode": "auto",
      "done": false,
      "completedAt": null,
      "position": 0,
      "createdAt": "2026-10-01T04:09:18.102Z",
      "updatedAt": "2026-10-01T04:09:18.102Z",
      "deletedAt": null
    },
    {
      "id": "item-12",
      "listId": "recebidos",
      "title": "[Access] Sample · Access to the finance system · Bruno",
      "description": "This is a sample request that needs approval. In step **8** of **Start here**, use **Move to… › Leadership approval** and approve it by completing it.\n\n- **What's needed:** read-only access to the finance system, to follow client payments.\n- **Why:** the sales team is taking over collections follow-up.\n- **Requested by:** Bruno, from Sales.\n- **Approval:** access to financial data goes through leadership.",
      "dueAt": null,
      "durationMinutes": null,
      "startAt": null,
      "startMode": "auto",
      "done": false,
      "completedAt": null,
      "position": 1,
      "createdAt": "2026-10-01T04:09:18.102Z",
      "updatedAt": "2026-10-01T04:09:18.102Z",
      "deletedAt": null
    }
  ],
  "notes": [],
  "messages": [],
  "pending": {
    "lists": [],
    "items": [],
    "notes": [],
    "messages": []
  }
}