Temsor integrations

• Action
  Close promise

  Marks an open call promise as kept or broken, with an optional short note, and returns the updated promise.

• Action
  Find calls by query

  Searches the call archive and returns the calls, call promises and extracted facts that match a text query, optionally narrowed by promise status, extension, competitor, date range or the extension a promise got stuck at.

• Action
  Get call

  Returns one call by its id, including its transfer path, handoff graph and count of open promises.

• Action
  List calls

  Returns the most recent calls in your Temsor call archive, with each call's direction, trunk, summary, transfer path and open promise count.

• Action
  List promises

  Returns the call promises tracked for agent handoff, filtered by status (open by default), each with its caller, promise text, transfer path and where it got stuck.

• Action
  Redact text

  Erases a caller's personal data from the Temsor call index — a promise, call, person, fact or utterance by id, or everything linked to a caller's phone number — by anonymizing or deleting it, and records an audit entry.

• Action
  Validate IBAN

  Validates an IBAN from any of 70+ countries, checking its checksum, country length and account structure, and returns the bank and branch codes plus a corrected suggestion when only the check digits are wrong.

• Action
  Validate phone number

  Validates a phone number and returns it in standard international (E.164) and national form, with its country and line type.

• Action
  Validate Turkish ID

  Validates a Turkish identifier — national ID (TCKN), tax number (VKN), IBAN, licence plate, IMEI, barcode, KEP address, MERSİS number, postal code or ISBN — detecting the type automatically when you don't specify it, and returns whether it is valid plus resolved details.

• Action
  Verify email

  Checks an email address: its syntax, whether the domain can receive mail, whether it is disposable or a role account, and suggests a correction for common domain typos.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.