Marc Alemany
Business Problem:
Many e-commerce teams in Poland and the wider CEE region run their store operations through BaseLinker, which consolidates orders from marketplaces (Allegro, eBay, Amazon, Shopify, WooCommerce, etc.) into one order management layer. When a customer messages on respond.io about an order, agents have no order context inside the conversation — they have to switch to BaseLinker, look up the order by customer name or order number, and copy details back to respond.io. This slows down replies and increases the chance of mistakes when handling delivery, refunds, or status questions.
Desired Outcome:
Add a native BaseLinker integration so agents and AI Agents can see and act on BaseLinker order data from inside respond.io conversations. At minimum: look up a contact's recent orders, view order status and tracking, and trigger basic actions (mark fulfilled, cancel, refund) without leaving respond.io.
Use Cases:
  • A support agent answering a "where is my order?" message can see the order status and tracking link without switching tools.
  • An AI Agent can answer order-status questions automatically by calling BaseLinker via the integration.
  • A sales agent following up after a checkout can see the order total and items to personalize the message.
Current Workaround:
Today teams either keep BaseLinker open in a second tab and copy details manually, or build a custom integration using respond.io's Workflow HTTP Request step against BaseLinker's API (requires Advanced plan + technical setup). There is no native option.