Skip to content
Pine Computer Request access
Menu

16 / 26 Assistants that finish the request · Example

Cancel a subscription

Every “before you go” offer is noted, and the plan is still cancelled before it renews.

Who it’s for
Assistants whose users ask them to cancel a plan or move to a cheaper one.
Why it’s hard
The cancel button sits behind pages of offers to stay, and one wrong click accepts a discount. A cancellation with no confirmation is hard to dispute when the next charge arrives.
You get back
  • Each provider’s confirmation, with the date it takes effect
  • The offers that were turned down
How it runs, in your product’s code

For each provider, a computer finds the plan page and works through to the change. Ironbark lets only the member change a plan, so your assistant asks in the chat and the person signs in on the screen there. Offers to stay are declined and written down. Each confirmation page is saved as a PDF in the conversation, with the date the change takes effect.

Ruby · example 
computer = pine.create_computer(  location: { country: "US" },  ephemeral: true)session = computer.create_session(name: "main", browser: true) session.agent.run(<<~JOB)  Move the gym membership to off-peak, and cancel the streaming  and meal-kit subscriptions before they renew.JOB session.agent.events do |event|  case event.type  when "needs_input"    # Your user takes the controls on the live desktop in your    # product, does what only they can, and hands them back.    session.agent.answer(event.payload["request_id"], "Done.")  when "result"    session.list_artifacts(turn_id: event.turn_id).each do |file|      row.attach(file.filename, session.read_artifact(file.id))    end    break if event.terminal?  endend computer.stop

Build more.
Hand AI the work.

Pine Computer is invite-only while in beta.