Features, Fixes: This is a thread of the

[leaden spindle]

1. Dynamic variables. Are these working properly now so that I can inject these into headers with {{}} notation and into properties by choosing Dynamic Variable from the dropdown for property type?

2. Webhook to register call ended. Is this available?

3. Can we get a feature to copy an agent? Agent setup can be quite complex. Spinning up a new agent is much more work than it would otherwise be if we had the ability to copy an agent.

4. Can we get "design time" variables? These would be like dynamic variables but rather than setting these at run time, they'd be set at design time. For example, if I've been setting up an agent in my staging environment, I'd like a design-time variable to point all my tools to my staging API server. Once the agent is approved for production, I'd like to simply set the variable to point to my production server. Instant production deployment!

5. Reorder property sequence in order to control the sequence of the dialogue with the caller.

[odd venture]

hey yossi, whats the thinking behind number 5

number 1 coming soon, 2 should be today, 3 is ready but let me check with jozef if we can push, 4 will be further away but will integrate nicely with our upcoming observability/testing suite

[leaden spindle]

Great, great. Thanks, Angelo. The thinking behind number five is that right now the agent asks the caller for their last name and then for their first name. It would be a little friendlier, a little more personal, if the agent would ask first for the first name and then for the last name. The order of the dialogue seems to flow from the order of the properties. So for us to have a degree of control over the dialogue, it would help to be able to re-order the properties to our liking. What do you think? Thanks!

[odd venture]

hm interesting, i haven't seen that before

[leaden spindle]

Here's my prompt for the body parameters. Note that I'm instructing it to ask first name, then last name.

However, the agent consistently asks for the last name before the first name. The only thing I can tie that to is that the lastName property is sequenced before the firstname property.

I'm wrong about this. I re-ordered the properties (just manually transposed them by renaming them and tweaking their descriptions) but the agent still asks for last name, then first name. Not the end of the world, but I wish I could figure out how to prompt it to reverse the order. I'm already instructing it to ask for first name, then last name. Maybe I can make the prompt more explicit.

6. Would love to save the configuration state of an agent so that if I play around with its configuration and find that I have not effected improvement, but rather I've regressed the quality of its behavior, it will be easy to revert to the latest saved checkpoint.

7. Is there a way to overwrite an existing Knowledge Base "article" with updated information? As it stand now, I am using the portal. I unlink it from its Agents. I delete it. I insert the new info. Then I relink the agents to the new KB "article". If I could programmatically update the existing article in place so that it will affect all linked agents at the next phone call, that will be fantastic!

Was able to get the agent to ask for first name, prior to last name. Evidently the LLM has some biases and you need to issue really strong instructions to the contrary in order to overcome them. Here's how I did it: