Early access From €0.25 an hour

An always on agent for tasks your team has no time for

Get started for free No credit card required Browse flows
  • Slack
  • Google Chat
  • Microsoft Teams
  • Linear
  • Jira
  • GitHub
  • GitLab

A customer report filed for planning Ready for a customer's renewal call The Friday status update A customer's question answered Release notes from what shipped

Search Acme

support

2

  1. Jonas

    @devboxes Müller GmbH and Brandt & Söhne both got their payment reminder twice, on Saturday and again on Monday. can you file it for billing in Linear? please don't fix it yet, Lisa wants to plan it in first

  2. devboxes APP

    Looked at 4 sources
    1. Slack Read this thread
    2. GitHub Found Tuesday's reminder change
    3. GitHub Read the weekend rule in the reminder job
    4. Linear Filed ENG-219 for billing

    Since Tuesday's release, reminders due on a weekend move to Monday, and the job still sends the weekend one too, so those customers get both. I filed ENG-219 for billing with a recommended fix and left the code as it is.

    Linear

    ENG-219 Weekend payment reminders go out twice

    Backlog Billing, Bug

    Filed ENG-219

Weekend payment reminders go out twice

  • Backlog
  • Medium
  • Billing
  • Bug

Reminders due on a Saturday or Sunday go out on that day and again on Monday.

Cause: Tuesday's release moves weekend reminders to Monday, and the weekend send still runs.

Recommended fix: drop the weekend send once a reminder has moved, and add a reminder due on a Saturday to the reminder tests.

Reported by Müller GmbH (INV-2026-311) and Brandt & Söhne.

Activity

  1. devboxes created the issue
  2. devboxes added the Billing label

Leave a comment…

Customer reports become issues with a recommended fix prepared

See the support flow

Weekend payment reminders go out twice

  • Backlog
  • Medium
  • Billing
  • Bug

Reminders due on a Saturday or Sunday go out on that day and again on Monday.

Cause: Tuesday's release moves weekend reminders to Monday, and the weekend send still runs.

Recommended fix: drop the weekend send once a reminder has moved, and add a reminder due on a Saturday to the reminder tests.

Reported by Müller GmbH (INV-2026-311) and Brandt & Söhne.

Activity

  1. devboxes created the issue
  2. devboxes added the Billing label

Leave a comment…

Ask what your team shipped and get the weekly update

See the changelog flow
Report posted by devboxes

Billing this week

  • Shipped Invoice PDFs continue on a second page when page one is full.
  • In progress Lena is fixing the weekend payment reminders that go out twice.
  • Blocked Quarterly billing waits for a decision on proration.
  • Next week English invoices start with the customer language setting.

Answers to your team's questions from your own past work

Search Acme

support

2

  1. Jonas

    @devboxes Müller GmbH asks why their reminder came on Monday this time instead of Saturday. did we change that on purpose?

  2. devboxes APP

    Looked at 3 sources
    1. Slack Read the #support thread about the double reminders
    2. Linear Read ENG-219 and its comments
    3. Slack Found the ledger 1.5.0 release notes in #billing

    Yes, on purpose. Since ledger 1.5.0, reminders due on a weekend or public holiday go out on the next working day, so Saturday's reminder moved to Monday. The double reminders Müller GmbH reported came from that change, and the fix in ENG-219 shipped in 1.5.1. The release notes explain it for customers.

    Linear

    ENG-219 Weekend payment reminders go out twice

    Done Billing, Bug

    devboxes

    ledger 1.5.0

    Changed: Payment reminders due on a weekend or public holiday go out on the next working day (#43).

  3. Jonas

    perfect, sending them the release notes

Ask the way you'd ask a colleague

Search Acme

support

2

  1. Jonas

    @devboxes customer says the CSV export skips orders placed after midnight. can you find out why and file it for the data team?

  2. devboxes APP

    Filed DATA-57 for the data team. The export cuts the day at midnight UTC, so orders placed after midnight Berlin time land in the next day's file. The issue has the customer's example and a recommended fix.

    Filed DATA-57

  3. Jonas

    @devboxes does a cancelled seat get refunded for the rest of the month? customer is asking

  4. devboxes APP

    Yes, for the days left in the month. The amount shows up as a credit on their next invoice. The billing code and the help center article on seats agree.

devboxes for support

Tell devboxes once how your team likes things done

Search Acme

support

2

  1. Jonas

    @devboxes from now on, when you answer a customer question here, add a reply I can paste to the customer. short, friendly, no ticket numbers

  2. devboxes Support APP

    Got it. In #support I'll add a short reply you can paste, in plain words.

  3. Jonas

    @devboxes a customer wants all of last year's invoices for their accountant. do they have to download them one by one?

  4. devboxes Support APP

    No. Since ledger 1.5.0 they can download a whole year as one ZIP file under Invoices, then Download year. To paste: "You can download all invoices from a year as one ZIP file: open Invoices and choose Download year."

Common processes devboxes can help you automate

All 84 flows

Hosted in Germany and running on your own model subscription

  1. Your tools

    Requests start where your team already works.

    • Slack
    • Google Chat
    • Microsoft Teams
    • Linear
    • Jira
    • GitHub
    • GitLab

  2. Servers in Germany

    Work runs on our servers in Germany or on a machine you register. We store your company's data encrypted on European-owned servers in Germany.

  3. Your model subscription

    The subscription or API key your team already pays for.

How we handle your data

Only pay for tasks

All chat interactions are billed to your own model subscription with no markup. Tasks spin up their own machine and are billed by the second.

See plans and prices

Where you land

Estimated cost per month

€50 €50

The estimate assumes an hour per task. Your model provider bills model usage directly.

200 tasks × 1 h × €0.25/hr

On your own machines, up to 3 tasks run at the same time for free, and further tasks cost €0.15 an hour.

What can I ask devboxes to do?

Anything you would ask a colleague who knows your product, such as answering a customer question, filing an issue, writing the weekly update or fixing a bug. If a request is unclear, devboxes asks before it starts.

Does everyone on the team need an account?

No. Anyone in a connected channel can ask devboxes. Only the person who sets it up needs an account.

How do I set it up?

Sign up, connect the chat or issue tracker your team uses, and invite devboxes to a channel. devboxes works with Slack, Google Chat, Microsoft Teams, Linear and Jira.

Can devboxes make mistakes?

Yes. devboxes uses AI models, and they can be wrong. Code changes always arrive as pull requests, so your team reviews them before anything ships.

Where is our data stored?

On our servers in Germany, or on machines you connect yourself.

What does it cost?

Tasks cost from €0.25 per machine hour. Answers in chat run on your own model subscription, so they're free. See pricing

Try devboxes with your team

Get started for free