Skip to content
Pine Computer Request access
Menu

19 / 26 Assistants that finish the request · Example

Resolve a support request

A damaged order is replaced and its delivery charge refunded once a team lead approves.

Who it’s for
Customer-support software whose requests can only be closed by working in two or three back offices.
Why it’s hard
A Tillpoint refund can’t be cancelled once issued, so a team lead approves each one.
You get back
  • The carrier’s delivery record, saved to the request
  • The replacement’s order number
  • The refund, issued after a team lead approved it
How it runs, in your product’s code

A computer opens a tab for each site the request needs. It finds the carrier’s note for order 20517, then places the replacement in the store. On Tillpoint it sets up a refund of the delivery charge and stops, and a team lead reads the amount on the screen below and clicks Approve refund. Each step is saved to the request as a file.

Ruby · example 
computer = pine.create_computer(  location: { country: "US" },  ephemeral: true)session = computer.create_session(name: "main", browser: true) session.agent.run(<<~JOB)  Order 20517 arrived damaged. Confirm it on the carrier’s  record and send a replacement. Refund the delivery charge once  a team lead approves.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.